Re: sysctl_doeproc() race

2018-03-10 Thread Kamil Rytarowski
On 10.03.2018 23:49, Robert Elz wrote: > Date:Sat, 10 Mar 2018 21:47:31 +0100 > From:Kamil Rytarowski > Message-ID: <6cbea372-5520-8d76-72ac-68409f5a3...@gmx.com> > > | This does not fix the race, > > Some races aren't worth fixing.What is the

Re: sysctl_doeproc() race

2018-03-10 Thread Robert Elz
Date:Sat, 10 Mar 2018 21:47:31 +0100 From:Kamil Rytarowski Message-ID: <6cbea372-5520-8d76-72ac-68409f5a3...@gmx.com> | This does not fix the race, Some races aren't worth fixing.What is the real issue here? | We will end up with the same

Re: sysctl_doeproc() race

2018-03-10 Thread Kamil Rytarowski
On 10.03.2018 21:47, Kamil Rytarowski wrote: > On 10.03.2018 20:45, Christos Zoulas wrote: >> In article , >> Kamil Rytarowski wrote: >>> I've been observing a race with the ptrace(2) ATF tests. >>> >>> There is a function

Re: sysctl_doeproc() race

2018-03-10 Thread Kamil Rytarowski
On 10.03.2018 20:45, Christos Zoulas wrote: > In article , > Kamil Rytarowski wrote: >> I've been observing a race with the ptrace(2) ATF tests. >> >> There is a function await_zombie() that checks whether a process (traced

Re: sysctl_doeproc() race

2018-03-10 Thread Christos Zoulas
In article , Kamil Rytarowski wrote: >I've been observing a race with the ptrace(2) ATF tests. > >There is a function await_zombie() that checks whether a process (traced >by a debugger) died and is now a zombie. The current