From: linmiaohe <linmiaohe@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/migrate: Avoid possible unnecessary ptrace_may_access() call in kernel_move_pages()
Date: Tue, 18 Aug 2020 02:25:49 +0000 [thread overview]
Message-ID: <8e7c7a77722446afbc8cb25e46eab325@huawei.com> (raw)
Matthew Wilcox <willy@infradead.org> wrote:
>On Mon, Aug 17, 2020 at 07:59:33AM -0400, Miaohe Lin wrote:
>> There is no need to check if this process has the right to modify the
>> specified process when they are same.
>
>We should probably also skip the security hook call if a process is modifying its own pages.
>
>How about this instead?
>
It sounds good, thanks for your good advice. Would you like a tag like suggest-by?
next reply other threads:[~2020-08-18 2:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 2:25 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-20 2:18 [PATCH] mm/migrate: Avoid possible unnecessary ptrace_may_access() call in kernel_move_pages() linmiaohe
2020-08-20 21:21 ` Kees Cook
2020-08-17 11:59 Miaohe Lin
2020-08-17 12:32 ` Matthew Wilcox
2020-08-19 18:04 ` Kees Cook
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=8e7c7a77722446afbc8cb25e46eab325@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).