Add the following flags to allow various restrictions on path
resolution (these affect the *entire* resolution, rather than just the
final path component -- as is the case with most other AT_* flags).
The primary justification for these flags is to allow for programs to be
far more strict about ho
On 2019-03-09, Linus Torvalds wrote:
> On Sat, Mar 9, 2019 at 9:26 AM Christian Brauner wrote:
> > Aside from that I want to point out that it is non-trivial to do this in
> > user space.
>
> Oh, absolutely agreed. It's easy to do it in the kernel, and doing it
> anywhere else ends up having hor
On Sat, Mar 9, 2019 at 9:26 AM Christian Brauner wrote:
>
> Aside from that I want to point out that it is non-trivial to do this in
> user space.
Oh, absolutely agreed. It's easy to do it in the kernel, and doing it
anywhere else ends up having horrible races that the kernel has to
deal with and
On Sat, Mar 09, 2019 at 09:00:58AM -0800, Linus Torvalds wrote:
> On Wed, Mar 6, 2019 at 11:14 AM Aleksa Sarai wrote:
> >
> > This is a refresh of Al's AT_NO_JUMPS patchset[1] (which was a variation
> > on David Drysdale's O_BENEATH patchset[2], which in turn was based on
> > the Capsicum project[
On Wed, Mar 6, 2019 at 11:14 AM Aleksa Sarai wrote:
>
> This is a refresh of Al's AT_NO_JUMPS patchset[1] (which was a variation
> on David Drysdale's O_BENEATH patchset[2], which in turn was based on
> the Capsicum project[3]). Input from Linus and Andy in the AT_NO_JUMPS
> thread[4] determined m
Add the following flags to allow various restrictions on path
resolution (these affect the *entire* resolution, rather than just the
final path component -- as is the case with most other AT_* flags).
The primary justification for these flags is to allow for programs to be
far more strict about ho
6 matches
Mail list logo
