Thread (12 messages) 12 messages, 4 authors, 2020-10-05

Re: [PATCH v2 0/3] block: fix up bio_crypt_ctx allocation

From: Eric Biggers <ebiggers@kernel.org>
Date: 2020-10-05 16:42:32
Also in: dm-devel

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:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help