Hi,

> Date: 2026-10-09 21:27:05+0200
> From: Alejandro Colomar <alx@kernel.org>
>
> 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.)

I've applied the patch.  Thanks!


Cheers,
Alex

> 
> > 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>



-- 
<https://www.alejandro-colomar.es>