From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.11-rc1
Date: Sun, 21 Jul 2024 16:52:25 -0700 [thread overview]
Message-ID: <20240721165225.0c96cdf1a51bcd7630b0afdc@linux-foundation.org> (raw)
In-Reply-To: <CAHk-=wjpx6uTAvjNnD5eipGjNYcwTgG9G6Dct=eLTfyzaaTy_g@mail.gmail.com>
On Sun, 21 Jul 2024 16:19:42 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sun, 21 Jul 2024 at 14:54, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > - 875fa64577da ("mm/hugetlb_vmemmap: fix race with speculative PFN
> > walkers") is known to cause a performance regression
> > (https://lore.kernel.org/all/3acefad9-96e5-4681-8014-827d6be71c7a@linux.ibm.com/T/#mfa809800a7862fb5bdf834c6f71a3a5113eb83ff).
> > Yu has a fix which I'll send along later via the hotfixes branch.
>
> That commit "875fa64577da" does not exist. I think you are talking
> about commit bd225530a4c7, which is in 6.10 and came in from your last
> hotfixes pull.
>
> I'm assuming 875fa64577da was some commit ID it had before getting
> rebased or something?
>
> I'm also a bit confused about why you mention this, since neither the
> cause _nor_ the fix are in this pull request and you have the wrong
> commit ID.
>
Yes, right, sorry. "mm/hugetlb_vmemmap: fix race with speculative PFN
walkers" was promoted into mm-hotfixes after I make this note.
Anyway. We broke a thing and it's being fixed.
next prev parent reply other threads:[~2024-07-21 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 21:54 Andrew Morton
2024-07-21 23:19 ` Linus Torvalds
2024-07-21 23:52 ` Andrew Morton [this message]
2024-07-21 23:59 ` Linus Torvalds
2024-07-22 0:14 ` Linus Torvalds
2024-07-22 1:15 ` pr-tracker-bot
2024-07-22 17:18 ` LEROY Christophe
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=20240721165225.0c96cdf1a51bcd7630b0afdc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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