On Fri, Mar 16, 2018 at 09:01:47AM -0700, Andy Lutomirski wrote:
>
>
> > On Mar 16, 2018, at 7:47 AM, Christian Brauner
> > wrote:
> >
> >> On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
>
>
> I bet I confused everyone with a blatant typo:
>
On Fri, Mar 16, 2018 at 09:01:47AM -0700, Andy Lutomirski wrote:
>
>
> > On Mar 16, 2018, at 7:47 AM, Christian Brauner
> > wrote:
> >
> >> On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
>
>
> I bet I confused everyone with a blatant typo:
>
> >>
> >> Hmm, I think we
> On Mar 16, 2018, at 7:47 AM, Christian Brauner
> wrote:
>
>> On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
I bet I confused everyone with a blatant typo:
>>
>> Hmm, I think we have to be very careful to avoid nasty races. I think
>> the
> On Mar 16, 2018, at 7:47 AM, Christian Brauner
> wrote:
>
>> On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
I bet I confused everyone with a blatant typo:
>>
>> Hmm, I think we have to be very careful to avoid nasty races. I think
>> the correct approach is to notice
On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:35 PM, Tycho Andersen wrote:
> > Hi Andy,
> >
> > On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> >> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn
On Fri, Mar 16, 2018 at 12:46:55AM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:35 PM, Tycho Andersen wrote:
> > Hi Andy,
> >
> > On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> >> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> >> > Hm, synchronously -
On Thu, Mar 15, 2018 at 5:35 PM, Tycho Andersen wrote:
> Hi Andy,
>
> On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
>> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
>> > Hm, synchronously - that brings to mind a thought... I should
On Thu, Mar 15, 2018 at 5:35 PM, Tycho Andersen wrote:
> Hi Andy,
>
> On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
>> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
>> > Hm, synchronously - that brings to mind a thought... I should re-look at
>> > Tycho's patches
Hi Andy,
On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> > Hm, synchronously - that brings to mind a thought... I should re-look at
> > Tycho's patches first, but, if I'm in a container, start some
Hi Andy,
On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> > Hm, synchronously - that brings to mind a thought... I should re-look at
> > Tycho's patches first, but, if I'm in a container, start some syscall that
> >
On Thu, Mar 15, 2018 at 5:25 PM, Christian Brauner
wrote:
> On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
>> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
>> > Quoting Andy Lutomirski (l...@kernel.org):
>> >> On Thu,
On Thu, Mar 15, 2018 at 5:25 PM, Christian Brauner
wrote:
> On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
>> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
>> > Quoting Andy Lutomirski (l...@kernel.org):
>> >> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
>> >>
On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> > Quoting Andy Lutomirski (l...@kernel.org):
> >> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
> >> wrote:
> >> >
On Thu, Mar 15, 2018 at 05:11:32PM +, Andy Lutomirski wrote:
> On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> > Quoting Andy Lutomirski (l...@kernel.org):
> >> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
> >> wrote:
> >> > On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho
On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> Quoting Andy Lutomirski (l...@kernel.org):
>> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
>> wrote:
>> > On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
>> >>
On Thu, Mar 15, 2018 at 5:05 PM, Serge E. Hallyn wrote:
> Quoting Andy Lutomirski (l...@kernel.org):
>> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
>> wrote:
>> > On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
>> >> Several months ago at Linux Plumber's, we had a
Quoting Andy Lutomirski (l...@kernel.org):
> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
> wrote:
> > On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
> >> Several months ago at Linux Plumber's, we had a discussion about adding a
> >> feature
Quoting Andy Lutomirski (l...@kernel.org):
> On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
> wrote:
> > On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
> >> Several months ago at Linux Plumber's, we had a discussion about adding a
> >> feature to seccomp which would allow
On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
wrote:
> On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
>> Several months ago at Linux Plumber's, we had a discussion about adding a
>> feature to seccomp which would allow seccomp to trigger a
On Thu, Mar 15, 2018 at 4:09 PM, Christian Brauner
wrote:
> On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
>> Several months ago at Linux Plumber's, we had a discussion about adding a
>> feature to seccomp which would allow seccomp to trigger a notification for
>> some
>> other
On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
> Several months ago at Linux Plumber's, we had a discussion about adding a
> feature to seccomp which would allow seccomp to trigger a notification for
> some
> other process. Here's a draft of that feature.
>
> Patch 1 contains
On Sun, Feb 04, 2018 at 11:49:43AM +0100, Tycho Andersen wrote:
> Several months ago at Linux Plumber's, we had a discussion about adding a
> feature to seccomp which would allow seccomp to trigger a notification for
> some
> other process. Here's a draft of that feature.
>
> Patch 1 contains
Several months ago at Linux Plumber's, we had a discussion about adding a
feature to seccomp which would allow seccomp to trigger a notification for some
other process. Here's a draft of that feature.
Patch 1 contains the bulk of it, patches 2 & 3 offer an alternative way to
acquire the fd that
Several months ago at Linux Plumber's, we had a discussion about adding a
feature to seccomp which would allow seccomp to trigger a notification for some
other process. Here's a draft of that feature.
Patch 1 contains the bulk of it, patches 2 & 3 offer an alternative way to
acquire the fd that
24 matches
Mail list logo