* Re: [PATCH] man/man2/rename.2: Remove CAP_MKNOD remark about whiteout creation
[not found] <20261009143656.4884-1-gnoack3000@gmail.com>
@ 2026-10-09 19:27 ` Alejandro Colomar
0 siblings, 0 replies; only message in thread
From: Alejandro Colomar @ 2026-10-09 19:27 UTC (permalink / raw)
To: Günther Noack; +Cc: Miklos Szeredi, linux-man
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread