From: "Jörn Engel" <joern@purestorage.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Uday Shankar <ushankar@purestorage.com>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [bug report?] unintuitive behavior when mapping over hugepage-backed PROT_NONE regions
Date: Sat, 8 Feb 2025 13:16:13 -0800 [thread overview]
Message-ID: <Z6fJnejWtQK5hn8r@cork> (raw)
In-Reply-To: <d50b6db5-9936-4cc1-85bd-708bf66df0bb@lucifer.local>
On Sat, Feb 08, 2025 at 06:00:39PM +0000, Lorenzo Stoakes wrote:
> On Sat, Feb 08, 2025 at 09:53:27AM -0800, Jörn Engel wrote:
>
> Funny you should mention that ;) we will soon no longer have this problem,
> and MAJOR efforts have gone into making this possible under RCU. The 6.12
> release was one long battle to get the key series in for this :P
>
> Which is in fact again Liam's aforementioned, a prerequisite for consistent
> observation of VMAs in /proc/$pid/[s]maps[_rollup].
You are my hero, Liam!
I looked at the issue some time ago and decided it was too hard to sort
out the mess.
Jörn
--
It's not whether you win or lose, it's how you place the blame.
-- unknown
prev parent reply other threads:[~2025-02-08 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 6:18 [bug report?] unintuitive behavior when mapping over hugepage-backed PROT_NONE regions Uday Shankar
2025-02-06 9:01 ` Oscar Salvador
2025-02-06 18:11 ` Jörn Engel
2025-02-06 18:54 ` Oscar Salvador
2025-02-07 10:29 ` Lorenzo Stoakes
2025-02-07 10:49 ` Vlastimil Babka
2025-02-07 12:33 ` Lorenzo Stoakes
2025-02-06 19:44 ` Uday Shankar
2025-02-07 13:12 ` Lorenzo Stoakes
2025-02-07 19:35 ` Jörn Engel
2025-02-08 16:02 ` Lorenzo Stoakes
2025-02-08 17:37 ` Jörn Engel
2025-02-08 17:40 ` Lorenzo Stoakes
2025-02-08 17:53 ` Jörn Engel
2025-02-08 18:00 ` Lorenzo Stoakes
2025-02-08 21:16 ` Jörn Engel [this message]
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=Z6fJnejWtQK5hn8r@cork \
--to=joern@purestorage.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=ushankar@purestorage.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.