[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231122133555.b7fc6cdefae0395d34a4cd1c@linux-foundation.org>
Date: Wed, 22 Nov 2023 13:35:55 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Gregory Price <gourry.memverge@...il.com>, linux-mm@...ck.org,
linux-doc@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-api@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd@...db.de, tglx@...utronix.de,
luto@...nel.org, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
mhocko@...nel.org, tj@...nel.org, ying.huang@...el.com,
Gregory Price <gregory.price@...verge.com>
Subject: Re: [RFC PATCH 00/11] mm/mempolicy: Make task->mempolicy externally
modifiable via syscall and procfs
On Wed, 22 Nov 2023 13:33:48 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed, 22 Nov 2023 16:11:49 -0500 Gregory Price <gourry.memverge@...il.com> wrote:
> > echo "default" > /proc/pid/mempolicy
> > echo "prefer=relative:0" > /proc/pid/mempolicy
> > echo "interleave:0-3" > /proc/pid/mempolicy
>
> What do we get when we read from this? Please add to changelog.
>
Also a description of the permissions for this procfs file, along with
reasoning. If it has global readability, and there's something
interesting in there, let's show that the security implications have
been fully considered.
Powered by blists - more mailing lists