GFP_KERNEL is not supposed to be ored with GFP_NOFS (the result is equivalent to GFP_KERNEL). Also, we use GFP_NOIO instead of GFP_NOFS, because we don't want any I/O being submitted in the direct reclaim path.
Signed-off-by: Mikulas Patocka <[email protected]> Cc: [email protected] # v5.4+ --- drivers/md/dm-crypt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: linux-2.6/drivers/md/dm-crypt.c =================================================================== --- linux-2.6.orig/drivers/md/dm-crypt.c 2020-01-02 14:16:21.000000000 +0100 +++ linux-2.6/drivers/md/dm-crypt.c 2020-01-02 14:16:21.000000000 +0100 @@ -717,7 +717,7 @@ static int crypt_iv_eboiv_gen(struct cry struct crypto_wait wait; int err; - req = skcipher_request_alloc(any_tfm(cc), GFP_KERNEL | GFP_NOFS); + req = skcipher_request_alloc(any_tfm(cc), GFP_NOIO); if (!req) return -ENOMEM; -- dm-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/dm-devel
