From: Alejandro Colomar <alx@kernel.org>
To: "Günther Noack" <gnoack3000@gmail.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/rename.2: Remove CAP_MKNOD remark about whiteout creation
Date: Fri, 9 Oct 2026 21:27:00 +0200 [thread overview]
Message-ID: <ask-80Zlt0ygw0pk@debian> (raw)
In-Reply-To: <20261009143656.4884-1-gnoack3000@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hi Günther,
> Date: 2026-10-09 16:36:56+0200
> From: Günther Noack <gnoack3000@gmail.com>
>
> Whiteout objects do not count as device files and do not require
> CAP_MKNOD since linux.git a3c751a50fe6 (2020-05-14; "vfs: allow
> unprivileged whiteout creation").
Thanks! I checked the referenced commit, and it seems correct.
Reviewed-by: Alejandro Colomar <alx@kernel.org>
(I'm not taking the patch yet, in case Miklos wants to comment, but
I will take it eventually.)
> Signed-off-by: Günther Noack <gnoack3000@gmail.com>
You forgot to CC the list. :)
Have a lovely night!
Alex
> ---
> man/man2/rename.2 | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/man/man2/rename.2 b/man/man2/rename.2
> index 14be6b20d3c9..7e5c02797230 100644
> --- a/man/man2/rename.2
> +++ b/man/man2/rename.2
> @@ -250,11 +250,6 @@ is ignored by the kernel's whiteout support code,
> as of Linux 4.19, at least.)
> .IP
> .B RENAME_WHITEOUT
> -requires the same privileges as creating a device node (i.e., the
> -.B CAP_MKNOD
> -capability).
> -.IP
> -.B RENAME_WHITEOUT
> can't be employed together with
> .BR RENAME_EXCHANGE .
> .IP
> --
> 2.56.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2026-10-09 19:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20261009143656.4884-1-gnoack3000@gmail.com>]
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=ask-80Zlt0ygw0pk@debian \
--to=alx@kernel.org \
--cc=gnoack3000@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mszeredi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.