The __GFP_NOWARN flag was included in GFP_NOWAIT since commit
16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT"). So
remove the redundant __GFP_NOWARN flag.

Signed-off-by: Fushuai Wang <wangfushuai@baidu.com>
---
 drivers/block/loop.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 053a086d547e..219f39f0afad 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -822,7 +822,7 @@ static void loop_queue_work(struct loop_device *lo, struct loop_cmd *cmd)
 	if (worker)
 		goto queue_work;
 
-	worker = kzalloc(sizeof(struct loop_worker), GFP_NOWAIT | __GFP_NOWARN);
+	worker = kzalloc(sizeof(struct loop_worker), GFP_NOWAIT);
 	/*
 	 * In the event we cannot allocate a worker, just queue on the
 	 * rootcg worker and issue the I/O as the rootcg
-- 
2.36.1

>> The __GFP_NOWARN flag was included in GFP_NOWAIT since commit
>> 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT"). So
>> remove the redundant __GFP_NOWARN flag.

I see that Qianfeng has already changed this, please ignore this.

Regards,
Wang.