Re: [v3 RFC PATCH 2/2] crypto: ecc: use caller's GFP flags

2017-07-18 Thread Tudor Ambarus
Hi, Herbert, On 07/18/2017 08:52 AM, Herbert Xu wrote: On Wed, Jun 28, 2017 at 05:08:36PM +0300, Tudor Ambarus wrote: Using GFP_KERNEL when allocating data and implicitly assuming that we can sleep was wrong because the caller could be in atomic context. Let the caller decide whether sleeping

Re: [v3 RFC PATCH 2/2] crypto: ecc: use caller's GFP flags

2017-07-17 Thread Herbert Xu
On Wed, Jun 28, 2017 at 05:08:36PM +0300, Tudor Ambarus wrote: > Using GFP_KERNEL when allocating data and implicitly > assuming that we can sleep was wrong because the caller > could be in atomic context. Let the caller decide whether > sleeping is possible or not. > > The caller (ecdh) was

[v3 RFC PATCH 2/2] crypto: ecc: use caller's GFP flags

2017-06-28 Thread Tudor Ambarus
Using GFP_KERNEL when allocating data and implicitly assuming that we can sleep was wrong because the caller could be in atomic context. Let the caller decide whether sleeping is possible or not. The caller (ecdh) was updated in the same patch in order to not affect bissectability.