On Sun, 2016-12-18 at 19:45 -0800, Davidlohr Bueso wrote:
> Nit: the title is a bit unclear. How about:
>
> ipc/sem.: fix semop() locking imbalance
>
> Otherwise, Ack.
(notices patchlet _not_ flying upstream... s/failure/imbalance?)
On Sun, 2016-12-18 at 19:45 -0800, Davidlohr Bueso wrote:
> Nit: the title is a bit unclear. How about:
>
> ipc/sem.: fix semop() locking imbalance
>
> Otherwise, Ack.
(notices patchlet _not_ flying upstream... s/failure/imbalance?)
Nit: the title is a bit unclear. How about:
ipc/sem.: fix semop() locking imbalance
Otherwise, Ack.
Thanks,
Davidlohr
Nit: the title is a bit unclear. How about:
ipc/sem.: fix semop() locking imbalance
Otherwise, Ack.
Thanks,
Davidlohr
Based on the syzcaller test case from dvyukov:
https://gist.githubusercontent.com/dvyukov/d0e5efefe4d7d6daed829f5c3ca26a40/raw/08d0a261fe3c987bed04fbf267e08ba04bd533ea/gistfile1.txt
The slow (i.e.: failure to acquire) syscall exit from semtimedop()
incorrectly assumed that the the same lock is
Based on the syzcaller test case from dvyukov:
https://gist.githubusercontent.com/dvyukov/d0e5efefe4d7d6daed829f5c3ca26a40/raw/08d0a261fe3c987bed04fbf267e08ba04bd533ea/gistfile1.txt
The slow (i.e.: failure to acquire) syscall exit from semtimedop()
incorrectly assumed that the the same lock is
6 matches
Mail list logo