Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall

2018-12-17 Thread Christian Brauner
On Thu, Dec 13, 2018 at 04:23:00PM -0600, Serge Hallyn wrote: > On Sat, Dec 08, 2018 at 06:40:59AM +0100, Christian Brauner wrote: > > The kill() syscall operates on process identifiers (pid). After a process > > has exited its pid can be reused by another process. If a caller sends a > > signal to

Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall

2018-12-13 Thread Serge E. Hallyn
On Sat, Dec 08, 2018 at 06:40:59AM +0100, Christian Brauner wrote: > The kill() syscall operates on process identifiers (pid). After a process > has exited its pid can be reused by another process. If a caller sends a > signal to a reused pid it will end up signaling the wrong process. This > issue

Re: [PATCH v5 1/1] signal: add pidfd_send_signal() syscall

2018-12-09 Thread kbuild test robot
Hi Christian, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.20-rc5] [cannot apply to next-20181207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

[PATCH v5 1/1] signal: add pidfd_send_signal() syscall

2018-12-07 Thread Christian Brauner
The kill() syscall operates on process identifiers (pid). After a process has exited its pid can be reused by another process. If a caller sends a signal to a reused pid it will end up signaling the wrong process. This issue has often surfaced and there has been a push to address this problem [1].