From: Dave Hansen <dave.hansen@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Vernon Yang <yanglincheng@kylinos.cn>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Orson Peters <orsonpeters@gmail.com>
Subject: Re: [GIT PULL] x86/urgent for 7.4-rc4
Date: Sun, 13 Sep 2026 18:12:57 -0700 [thread overview]
Message-ID: <3e4f6c01-012b-4730-b34d-d8264772f770@intel.com> (raw)
In-Reply-To: <CAHk-=wj3H5DdeRqnWWz7PwH1Qzb1PgQWf9S0Ce3BjZ+68LjXuQ@mail.gmail.com>
On 9/13/26 18:04, Linus Torvalds wrote:
> On Sun, 13 Sept 2026 at 17:18, Dave Hansen <dave.hansen@intel.com> wrote:
...
> This does not seem to be a bug in MADV_FREE at all, and isn't even
> really related to MADV_FREE. I think MADV_FREE just happened to be a
> way to trigger it.
Ahh, I see your point. Agreed. It's really about mprotect() on a PMD
versus the dirty bit.
> I'd love for somebody to hit me with a clue hammer on how this all
> happened, but I guess that's not required for the fix.
Rick dug back in some old versions of the shadow stack patches to look
for the origin:
> https://lore.kernel.org/lkml/c15c2b17e110782d966751dbf3c487a6db837a87.camel@intel.com/
It does seem to just be cruft from old versions that snuck through as
opposed to something intentional.
next prev parent reply other threads:[~2026-09-14 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 22:53 Dave Hansen
2026-09-13 23:10 ` Linus Torvalds
2026-09-13 23:23 ` Linus Torvalds
2026-09-14 0:18 ` Dave Hansen
2026-09-14 1:04 ` Linus Torvalds
2026-09-14 1:12 ` Dave Hansen [this message]
2026-09-14 10:12 ` Orson Peters
2026-09-14 16:36 ` Linus Torvalds
2026-09-14 1:09 ` pr-tracker-bot
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=3e4f6c01-012b-4730-b34d-d8264772f770@intel.com \
--to=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonpeters@gmail.com \
--cc=rick.p.edgecombe@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yanglincheng@kylinos.cn \
/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
all inboxes | Powered by JetHome®