From: chenguanyou <chenguanyou9338@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, keescook@chromium.org,
mhocko@suse.com, lukas.bulwahn@gmail.com, vbabka@suse.cz,
gpiccoli@canonical.com, chenguanyou <chenguanyou@xiaomi.com>
Subject: [PATCH] [fuse] alloc_page nofs avoid deadlock
Date: Thu, 3 Jun 2021 20:41:05 +0800 [thread overview]
Message-ID: <20210603124105.29052-1-chenguanyou@xiaomi.com> (raw)
ABA deadlock
PID: 17172 TASK: ffffffc0c162c000 CPU: 6 COMMAND: "Thread-21"
PID: 9652 TASK: ffffffc0c9ce0000 CPU: 4 COMMAND: "kworker/u16:8"
Signed-off-by: chenguanyou <chenguanyou@xiaomi.com>
---
fs/fuse/dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index c0fee830a34e..d36125ff0405 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -721,7 +721,7 @@ static int fuse_copy_fill(struct fuse_copy_state *cs)
if (cs->nr_segs >= cs->pipe->max_usage)
return -EIO;
- page = alloc_page(GFP_HIGHUSER);
+ page = alloc_page(GFP_NOFS | __GFP_HIGHMEM);
if (!page)
return -ENOMEM;
--
2.17.1
next reply other threads:[~2021-06-03 12:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 12:41 chenguanyou [this message]
2021-06-03 12:56 ` [PATCH] [fuse] alloc_page nofs avoid deadlock Michal Hocko
2021-06-03 12:52 chenguanyou
2021-06-08 15:30 ` Miklos Szeredi
2021-07-13 2:42 ` Ed Tsai
2021-08-18 9:24 ` Miklos Szeredi
2021-09-24 3:52 ` Ed Tsai
2021-09-24 7:52 ` Miklos Szeredi
2021-09-28 15:25 ` Miklos Szeredi
2021-12-14 9:25 ` Ed Tsai
2021-12-14 9:38 ` Greg Kroah-Hartman
2021-12-15 8:22 ` Ed Tsai
2021-12-15 13:52 ` Greg Kroah-Hartman
[not found] ` <SI2PR03MB5545E0B76E54013678B9FEEC8BA99@SI2PR03MB5545.apcprd03.prod.outlook.com>
2022-06-10 7:48 ` Ed Tsai
2022-06-13 8:45 ` Miklos Szeredi
2022-06-13 9:29 ` Ed Tsai
2022-07-11 7:49 ` Miklos Szeredi
2022-07-12 1:16 ` Ed Tsai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210603124105.29052-1-chenguanyou@xiaomi.com \
--to=chenguanyou9338@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenguanyou@xiaomi.com \
--cc=gpiccoli@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).