[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <obqnuxousf64hdkaatumcxsqcrinr5scuufepazhzfz6waapnm@nze4eag2wljd>
Date: Tue, 28 Jan 2025 16:28:03 -0800
From: Shakeel Butt <shakeel.butt@...ux.dev>
To: Andrii Nakryiko <andrii@...nel.org>
Cc: linux-mm@...ck.org, akpm@...ux-foundation.org,
linux-fsdevel@...r.kernel.org, brauner@...nel.org, viro@...iv.linux.org.uk,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org, kernel-team@...a.com, rostedt@...dmis.org,
peterz@...radead.org, mingo@...nel.org, linux-trace-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, rppt@...nel.org, liam.howlett@...cle.com, surenb@...gle.com,
kees@...nel.org, jannh@...gle.com
Subject: Re: [PATCH] docs,procfs: document /proc/PID/* access permission
checks
On Tue, Jan 28, 2025 at 04:17:47PM -0800, Andrii Nakryiko wrote:
> Add a paragraph explaining what sort of capabilities a process would
> need to read procfs data for some other process. Also mention that
> reading data for its own process doesn't require any extra permissions.
>
> Signed-off-by: Andrii Nakryiko <andrii@...nel.org>
Reviewed-by: Shakeel Butt <shakeel.butt@...ux.dev>
Powered by blists - more mailing lists