Re: [PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-24 Thread Herbert Xu
On Fri, Nov 24, 2017 at 05:04:19PM +0100, Stephan Mueller wrote: > > Would it make sense to feed it to stable? I already added stable Cc's so it should go in automatically once it's pushed to Linus. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gon

Re: [PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-24 Thread Jonathan Cameron
On Fri, 24 Nov 2017 17:04:19 +0100 Stephan Mueller wrote: > Am Freitag, 24. November 2017, 08:37:39 CET schrieb Herbert Xu: > > Hi Herbert, > > > On Fri, Nov 10, 2017 at 01:20:55PM +0100, Stephan Müller wrote: > > > The code paths protected by the socket-lock do not use or modify the > > > so

Re: [PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-24 Thread Stephan Mueller
Am Freitag, 24. November 2017, 08:37:39 CET schrieb Herbert Xu: Hi Herbert, > On Fri, Nov 10, 2017 at 01:20:55PM +0100, Stephan Müller wrote: > > The code paths protected by the socket-lock do not use or modify the > > socket in a non-atomic fashion. The actions pertaining the socket do not > > e

Re: [PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-24 Thread Herbert Xu
On Fri, Nov 10, 2017 at 01:20:55PM +0100, Stephan Müller wrote: > The code paths protected by the socket-lock do not use or modify the > socket in a non-atomic fashion. The actions pertaining the socket do not > even need to be handled as an atomic operation. Thus, the socket-lock > can be safely i

Re: [PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-10 Thread Romain Izard
2017-11-10 13:20 GMT+01:00 Stephan Müller : > The code paths protected by the socket-lock do not use or modify the > socket in a non-atomic fashion. The actions pertaining the socket do not > even need to be handled as an atomic operation. Thus, the socket-lock > can be safely ignored. > > This fix

[PATCH v3] crypto: AF_ALG - remove locking in async callback

2017-11-10 Thread Stephan Müller
The code paths protected by the socket-lock do not use or modify the socket in a non-atomic fashion. The actions pertaining the socket do not even need to be handled as an atomic operation. Thus, the socket-lock can be safely ignored. This fixes a bug regarding scheduling in atomic as the callback