From: Michal Hocko <mhocko@suse.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jan Stancek <jstancek@redhat.com>,
otto ebeling <otto.ebeling@iki.fi>,
mtk manpages <mtk.manpages@gmail.com>,
linux-mm@kvack.org, w@1wt.eu, keescook@chromium.org,
ltp@lists.linux.it,
Linus Torvalds <torvalds@linux-foundation.org>,
Cristopher Lameter <cl@linux.com>
Subject: Re: migrate_pages() of process with same UID in 4.15-rcX
Date: Mon, 29 Jan 2018 14:57:47 +0100 [thread overview]
Message-ID: <20180129135747.GG21609@dhcp22.suse.cz> (raw)
In-Reply-To: <20180129133151.GF21609@dhcp22.suse.cz>
[Fixup Christoph email - the thread starts here
http://lkml.kernel.org/r/1394749328.5225281.1515598510696.JavaMail.zimbra@redhat.com]
On Mon 29-01-18 14:31:51, Michal Hocko wrote:
> [Sorry for a very late reply]
>
> On Wed 10-01-18 10:21:31, Eric W. Biederman wrote:
> [...]
> > All of that said. I am wondering if we should have used
> > PTRACE_MODE_READ_FSCREDS on these permission checks.
>
> If this is really about preventing the layout discovery then we should
> be in sync with proc_mem_open and that uses PTRACE_MODE_FSCREDS|PTRACE_MODE_READ
> Should we do the same thing here?
> --
> Michal Hocko
> SUSE Labs
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-29 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1243932888.5206621.1515594158029.JavaMail.zimbra@redhat.com>
2018-01-10 15:35 ` migrate_pages() of process with same UID in 4.15-rcX Jan Stancek
2018-01-10 16:21 ` Eric W. Biederman
2018-01-29 13:31 ` Michal Hocko
2018-01-29 13:57 ` Michal Hocko [this message]
2018-03-12 9:46 ` Otto Ebeling
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=20180129135747.GG21609@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=cl@linux.com \
--cc=ebiederm@xmission.com \
--cc=jstancek@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=ltp@lists.linux.it \
--cc=mtk.manpages@gmail.com \
--cc=otto.ebeling@iki.fi \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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).