block: fix up bio_crypt_ctx allocation
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest3 patches 8 repliesIn review
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block: make bio_crypt_clone() able to failblock/ block/ block/ +2 more | +42 | 2 replies | |
| 2/3 | block: make blk_crypto_rq_bio_prep() able to failblock/ block/ block/ +1 more | +34 | 2 replies | |
| 3/3 | block: warn if !__GFP_DIRECT_RECLAIM in bio_crypt_set_ctx()block/ | +9 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Satya Tangirala | Mike Snitzer |
|---|---|---|
| 1/3 | R-b | R-b |
| 2/3 | R-b | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/3] block: fix up bio_crypt_ctx allocation
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/[email protected]):
- 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
Signature · 1 line
2.28.0