From: Alex Colomar <alx.manpages@gmail.com>
To: Zach OKeefe <zokeefe@google.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Yang Shi <shy828301@gmail.com>,
linux-mm@kvack.org, linux-man@vger.kernel.org
Subject: Re: [PATCH man-pages 3/4] process_madvise.2: CAP_SYS_ADMIN cleanup
Date: Tue, 18 Oct 2022 12:38:24 +0200 [thread overview]
Message-ID: <95dd505c-40cd-b4f3-c510-1f21dcb77f1d@gmail.com> (raw)
In-Reply-To: <20221017175523.2048887-4-zokeefe@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]
Hi Zach,
On 10/17/22 19:55, Zach OKeefe wrote:
> From: Zach O'Keefe <zokeefe@google.com>
>
> Since commit 96cfe2c0fd23 ("mm/madvise: replace ptrace attach
> requirement for process_madvise"), process_madvise(2) has only
> required CAP_SYS_NICE capability. Update the man page to reflect this.
>
> Signed-off-by: Zach O'Keefe <zokeefe@google.com>
> ---
> man2/process_madvise.2 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man2/process_madvise.2 b/man2/process_madvise.2
> index 6208206e4..7bee1a098 100644
> --- a/man2/process_madvise.2
> +++ b/man2/process_madvise.2
> @@ -113,7 +113,8 @@ check (see
> in addition,
> because of the performance implications of applying the advice,
> the caller must have the
> -.B CAP_SYS_ADMIN
> +.\" commit 96cfe2c0fd23ea7c2368d14f769d287e7ae1082e
> +.B CAP_SYS_NICE
Would it make sense to keep some parentheses specifying that in old
kernels CAP_SYS_ADMIN was requiring instead?
Cheers,
Alex
> capability.
> .SH RETURN VALUE
> On success,
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-18 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 17:55 [PATCH 0/4] Add MADV_COLLAPSE documentation Zach OKeefe
2022-10-17 17:55 ` [PATCH man-pages 1/4] madvise.2: update THP file/shmem documentation for +5.4 Zach OKeefe
2022-10-18 10:32 ` Alex Colomar
2022-10-18 16:52 ` Zach O'Keefe
2022-10-17 17:55 ` [PATCH man-pages 2/4] madvise.2: document reliable probe for advice support Zach OKeefe
2022-10-18 10:36 ` Alex Colomar
2022-10-18 17:53 ` Zach O'Keefe
2022-10-18 18:04 ` Alejandro Colomar
2022-10-18 18:30 ` Zach O'Keefe
2022-10-17 17:55 ` [PATCH man-pages 3/4] process_madvise.2: CAP_SYS_ADMIN cleanup Zach OKeefe
2022-10-18 10:38 ` Alex Colomar [this message]
2022-10-18 21:22 ` Zach O'Keefe
2022-10-17 17:55 ` [PATCH man-pages 4/4] madvise.2: add documentation for MADV_COLLAPSE Zach OKeefe
2022-10-18 10:47 ` Alex Colomar
2022-10-18 21:54 ` Zach O'Keefe
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=95dd505c-40cd-b4f3-c510-1f21dcb77f1d@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=shy828301@gmail.com \
--cc=zokeefe@google.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