Mike Larkin(mlar...@azathoth.net) on 2018.06.25 19:31:40 -0700:
> On Mon, Jun 25, 2018 at 01:29:36PM +0200, Martin Pieuchot wrote:
> > On 20/06/18(Wed) 13:13, Martin Pieuchot wrote:
> > > Diff below unlocks the following syscalls:
> > >
> > > recvmsg(2), recvfrom(2), accept(2), getpeername(2),
On 26.06.18 11:47, Martin Pieuchot wrote:
> On 26/06/18(Tue) 10:46, Bruno Flueckiger wrote:
> > On 20.06.2018 13:13, Martin Pieuchot wrote:
> > > Diff below unlocks the following syscalls:
> > >
> > > recvmsg(2), recvfrom(2), accept(2), getpeername(2), getsockname(2),
> > > accept4(2),
On 20.06.2018 13:13, Martin Pieuchot wrote:
Diff below unlocks the following syscalls:
recvmsg(2), recvfrom(2), accept(2), getpeername(2), getsockname(2),
accept4(2), connect(2), bind(2), setsockopt(2), listen(2),
getsockopt(2), shutdown(2)
It doesn't mean that they won't run without the
On Mon, Jun 25, 2018 at 01:29:36PM +0200, Martin Pieuchot wrote:
> On 20/06/18(Wed) 13:13, Martin Pieuchot wrote:
> > Diff below unlocks the following syscalls:
> >
> > recvmsg(2), recvfrom(2), accept(2), getpeername(2), getsockname(2),
> > accept4(2), connect(2), bind(2), setsockopt(2),
On 20/06/18(Wed) 13:13, Martin Pieuchot wrote:
> Diff below unlocks the following syscalls:
>
> recvmsg(2), recvfrom(2), accept(2), getpeername(2), getsockname(2),
> accept4(2), connect(2), bind(2), setsockopt(2), listen(2),
> getsockopt(2), shutdown(2)
>
> It doesn't mean that they won't
Diff below unlocks the following syscalls:
recvmsg(2), recvfrom(2), accept(2), getpeername(2), getsockname(2),
accept4(2), connect(2), bind(2), setsockopt(2), listen(2),
getsockopt(2), shutdown(2)
It doesn't mean that they won't run without the KERNEL_LOCK(). Instead
a lock will be picked
