| Message ID | 20200916035315.34046-1-ebiggers@kernel.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | block: fix up bio_crypt_ctx allocation | expand |
On Tue, Sep 15, 2020 at 08:53:12PM -0700, Eric Biggers wrote: > This series makes allocation of encryption contexts either able to fail, > or explicitly require __GFP_DIRECT_RECLAIM (via WARN_ON_ONCE). > > This applies to linux-block/for-next. > > Changed since v1 (https://lkml.kernel.org/r/20200902051511.79821-1-ebiggers@kernel.org): > - Added patches 2 and 3. > - Added kerneldoc for bio_crypt_clone(). > - Adjusted commit message. > > Eric Biggers (3): > block: make bio_crypt_clone() able to fail > block: make blk_crypto_rq_bio_prep() able to fail > block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx() Jens, any interest in applying these patches for 5.10? - Eric
On Mon, Sep 28, 2020 at 01:59:34PM -0700, Eric Biggers wrote: > On Tue, Sep 15, 2020 at 08:53:12PM -0700, Eric Biggers wrote: > > This series makes allocation of encryption contexts either able to fail, > > or explicitly require __GFP_DIRECT_RECLAIM (via WARN_ON_ONCE). > > > > This applies to linux-block/for-next. > > > > Changed since v1 (https://lkml.kernel.org/r/20200902051511.79821-1-ebiggers@kernel.org): > > - Added patches 2 and 3. > > - Added kerneldoc for bio_crypt_clone(). > > - Adjusted commit message. > > > > Eric Biggers (3): > > block: make bio_crypt_clone() able to fail > > block: make blk_crypto_rq_bio_prep() able to fail > > block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx() > > Jens, any interest in applying these patches for 5.10? > Ping.
On 9/15/20 9:53 PM, Eric Biggers wrote: > This series makes allocation of encryption contexts either able to fail, > or explicitly require __GFP_DIRECT_RECLAIM (via WARN_ON_ONCE). > > This applies to linux-block/for-next. > > Changed since v1 (https://lkml.kernel.org/r/20200902051511.79821-1-ebiggers@kernel.org): > - Added patches 2 and 3. > - Added kerneldoc for bio_crypt_clone(). > - Adjusted commit message. Applied for 5.10, thanks.
This series makes allocation of encryption contexts either able to fail, or explicitly require __GFP_DIRECT_RECLAIM (via WARN_ON_ONCE). This applies to linux-block/for-next. Changed since v1 (https://lkml.kernel.org/r/20200902051511.79821-1-ebiggers@kernel.org): - Added patches 2 and 3. - Added kerneldoc for bio_crypt_clone(). - Adjusted commit message. Eric Biggers (3): block: make bio_crypt_clone() able to fail block: make blk_crypto_rq_bio_prep() able to fail block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx() block/bio.c | 20 +++++++++----------- block/blk-core.c | 8 +++++--- block/blk-crypto-internal.h | 21 ++++++++++++++++----- block/blk-crypto.c | 33 ++++++++++++++++++++------------- block/blk-mq.c | 7 ++++++- block/bounce.c | 19 +++++++++---------- drivers/md/dm.c | 7 ++++--- include/linux/blk-crypto.h | 20 ++++++++++++++++---- 8 files changed, 85 insertions(+), 50 deletions(-) base-commit: 99faa39ec56f33591ed3cc4d3ef62ac2878fad7e