From: Lorenzo Stoakes <ljs@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
David Hildenbrand <david@kernel.org>,
Jann Horn <jannh@google.com>, Kees Cook <kees@kernel.org>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm_access: simplify the security checks
Date: Mon, 1 Jun 2026 12:16:49 +0100 [thread overview]
Message-ID: <ah1pqCoH6guhnj8X@lucifer> (raw)
In-Reply-To: <ahrvv-XGt8SiZUvW@redhat.com>
On Sat, May 30, 2026 at 04:10:07PM +0200, Oleg Nesterov wrote:
> On 05/30, Oleg Nesterov wrote:
> >
> > 2. With the change above may_access_mm() doesn't need the "mm" argument,
> > so we do not need to call get_task_mm() beforehand, we can call it
> > only if may_access_mm() suceeds.
> >
> > 2. With the change above, may_access_mm() doesn't need the "mm" argument,
> > so we do not need to call get_task_mm() beforehand. We can call it
> > only if may_access_mm() succeeds.
>
> OOPS. Somehow I wrote the same twice. Will fix the changelog and send V2
> in reply to this patch...
Sorry, pedantic side-note here but - in general in mm we prefer you don't send
new revision in-reply-to the prior one, as it makes them easier to miss! :)
>
> Oleg.
>
Cheers, Lorenzo
next prev parent reply other threads:[~2026-06-01 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 13:56 Oleg Nesterov
2026-05-30 14:10 ` Oleg Nesterov
2026-06-01 11:16 ` Lorenzo Stoakes [this message]
2026-05-30 14:12 ` [PATCH v2] " Oleg Nesterov
2026-06-01 12:04 ` David Hildenbrand (Arm)
2026-06-01 12:31 ` Oleg Nesterov
2026-06-01 12:12 ` Lorenzo Stoakes
2026-06-01 12:42 ` Oleg Nesterov
2026-05-30 15:00 ` [PATCH] " Oleg Nesterov
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=ah1pqCoH6guhnj8X@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.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
all inboxes | Powered by JetHome®