Re: [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check

Quoting Serge E. Hallyn ([email protected]):
> Quoting Satyam Sharma ([email protected]):
> > From: Satyam Sharma <[email protected]>
> > 
> > [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check
> > 
> > Introduce is_owner_or_cap() macro in fs.h, and convert over relevant
> > users to it. This is done because we want to avoid bugs in the future
> 
> I like the idea - it will make future user namespace/per-container
> capability patches much cleaner by localizing a lot of the changes.
> 
> (haven't tested the patch yet, but it looks trivial enough, and I will
> test later today)

tested fine for me.

thanks,
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check
  - From: Satyam Sharma <[email protected]>
- Re: [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check
  - From: "Serge E. Hallyn" <[email protected]>

Prev by Date: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
Next by Date: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
Previous by thread: Re: [PATCH] Introduce is_owner_or_cap() to wrap CAP_FOWNER use with fsuid check
Next by thread: Re: [PATCH] modpost white list pattern adjustment
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]