[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250809142240.174197-1-rongqianfeng@vivo.com>
Date: Sat, 9 Aug 2025 22:22:39 +0800
From: Qianfeng Rong <rongqianfeng@...o.com>
To: Yu Kuai <yukuai3@...wei.com>,
Jens Axboe <axboe@...nel.dk>,
linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Qianfeng Rong <rongqianfeng@...o.com>
Subject: [PATCH] block, bfq: remove redundant __GFP_NOWARN
Commit 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT") made
GFP_NOWAIT implicitly include __GFP_NOWARN.
Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT (e.g.,
`GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean up these
redundant flags across subsystems.
Signed-off-by: Qianfeng Rong <rongqianfeng@...o.com>
---
block/bfq-iosched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
index 3bf76902f07f..db0ae65186ec 100644
--- a/block/bfq-iosched.c
+++ b/block/bfq-iosched.c
@@ -5848,7 +5848,7 @@ static struct bfq_queue *bfq_get_queue(struct bfq_data *bfqd,
}
bfqq = kmem_cache_alloc_node(bfq_pool,
- GFP_NOWAIT | __GFP_ZERO | __GFP_NOWARN,
+ GFP_NOWAIT | __GFP_ZERO,
bfqd->queue->node);
if (bfqq) {
--
2.34.1
Powered by blists - more mailing lists