From: Andrew Morton <akpm@linux-foundation.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
Suren Baghdasaryan <surenb@google.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org
Subject: Re: [PATCH] fs/proc/task_mmu: fix missed VMAs when reading /proc/PID/maps and friends
Date: Mon, 26 Oct 2026 08:56:36 -0700 [thread overview]
Message-ID: <20261026085636.4cc194fdd7aad8e7d3e68c4e@linux-foundation.org> (raw)
In-Reply-To: <44405019-7494-446a-86b4-05b2ac03f768@kernel.org>
On Mon, 26 Oct 2026 11:04:23 +0100 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
> >
> > PROCMAP_QUERY does the same fresh lookup, shouldn't d9d1c2d81797
> > ("fs/proc/task_mmu: execute PROCMAP_QUERY ioctl under per-vma locks") be
> > here as well? (commit tracked down by an LLM)
>
> Hm, very likely I missed that. So yeah, let's just add it. I assume it won't
> matter much because 5631da56c9a8 is the oldest one either way.
I made that change to the mm.git copy of this patch.
next prev parent reply other threads:[~2026-10-26 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 10:43 [PATCH] fs/proc/task_mmu: fix missed VMAs when reading /proc/PID/maps and friends David Hildenbrand (Arm)
2026-10-25 14:55 ` Suren Baghdasaryan
2026-10-25 19:01 ` Jose A. Perez de Azpillaga
2026-10-26 10:04 ` David Hildenbrand (Arm)
2026-10-26 15:56 ` Andrew Morton [this message]
2026-10-26 13:35 ` Lorenzo Stoakes (ARM)
2026-10-26 13:38 ` Lorenzo Stoakes (ARM)
2026-10-26 16:16 ` Suren Baghdasaryan
2026-10-26 17:19 ` David Hildenbrand (Arm)
2026-10-26 17:26 ` Lorenzo Stoakes (ARM)
2026-10-26 18:01 ` Liam R. Howlett
2026-10-26 18:05 ` Lorenzo Stoakes (ARM)
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=20261026085636.4cc194fdd7aad8e7d3e68c4e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=azpijr@gmail.com \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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 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.