crypto: user - Replace GFP_ATOMIC with GFP_KERNEL in crypto_report
authorJia-Ju Bai <baijiaju1990@gmail.com>
Thu, 25 Jan 2018 10:06:02 +0000 (18:06 +0800)
committerHerbert Xu <herbert@gondor.apana.org.au>
Thu, 15 Feb 2018 15:26:47 +0000 (23:26 +0800)
After checking all possible call chains to crypto_report here,
my tool finds that crypto_report is never called in atomic context.
And crypto_report calls crypto_alg_match which calls down_read,
thus it proves again that crypto_report can call functions which may sleep.
Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL.

This is found by a static analysis tool named DCNS written by myself.

Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto/crypto_user.c

index 5c291eedaa7029427513521ace34aea2cf9e1ff7..0e89b5457cab0b2d6f2ba684b23440b9b1544c4a 100644 (file)
@@ -271,7 +271,7 @@ static int crypto_report(struct sk_buff *in_skb, struct nlmsghdr *in_nlh,
                return -ENOENT;
 
        err = -ENOMEM;
-       skb = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_ATOMIC);
+       skb = nlmsg_new(NLMSG_DEFAULT_SIZE, GFP_KERNEL);
        if (!skb)
                goto drop_alg;