linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-mm@kvack.org,  mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org,  Huang Ying <ying.huang@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] MM updates for 6.12-rc1
Date: Sun, 22 Sep 2024 11:32:35 +0200	[thread overview]
Message-ID: <CAMuHMdW-4_WvazciLPedP6R6XnEnHqsEh+3s7M5159zcmHit9w@mail.gmail.com> (raw)
In-Reply-To: <20240920023317.f20c9ecbb2a2f4bf382d831c@linux-foundation.org>

Hi Andrew,

On Fri, Sep 20, 2024 at 11:34 AM Andrew Morton
<akpm@linux-foundation.org> wrote:
> Linus, please merge this cycle's batch of MM updates, thanks.
>
> Conflicts which I'm seeing, along with their linux-next resolutions are
> as follows:

[...]

> kernel/resource.c, vs ea72ce5da228 ("x86/kaslr: Expose and use the end
> of the physical memory address space"):
> https://lkml.kernel.org/r/20240909100043.60668995@canb.auug.org.au

[...]

> A build fix for m68k is needed, vs ea72ce5da228 ("x86/kaslr: Expose and
> use the end of the physical memory address space").  See
> https://lkml.kernel.org/r/87ttenvw0i.fsf@yhuang6-desk2.ccr.corp.intel.com

Which is not sufficient, as kisskb reports for m68k:

    kernel/resource.c: In function ‘gfr_start’:
    ./include/linux/minmax.h:93:30: error: conversion from ‘long long
unsigned int’ to ‘resource_size_t’ {aka ‘unsigned int’} changes value
from ‘18446744073709551615’ to ‘4294967295’ [-Werror=overflow]

Due to

    #define PHYSMEM_END  (-1ULL)

not being correct on 32-bit without LPAE.
Presumably this should just take into account the actual size of
phys_addr_t. My head is too hazy after Vienna to send a patch now ;-)

I bisected this to 99185c10d5d9214d ("resource, kunit: add test case
for region_intersects()"),  but apparently the offending definition
was modified later in commits ea72ce5da22806d5 ("x86/kaslr:
Expose and use the end of the physical memory address space")
and 617a814f14b89142 ("Merge tag 'mm-stable-2024-09-20-02-31' of
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm").

> The following changes since commit 431c1646e1f86b949fa3685efc50b660a364c2b6:

[...]

> "resource: Fix region_intersects() vs add_memory_driver_managed()" from
> Huang Ying.  Fix a bug in region_intersects() for systems with CXL memory.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds


  parent reply	other threads:[~2024-09-22  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20  9:33 Andrew Morton
2024-09-21 15:49 ` pr-tracker-bot
2024-09-22  9:32 ` Geert Uytterhoeven [this message]
2024-09-22 16:34   ` Linus Torvalds
2024-09-23  8:09     ` Geert Uytterhoeven
2024-09-23 16:13       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMuHMdW-4_WvazciLPedP6R6XnEnHqsEh+3s7M5159zcmHit9w@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox