From: Shigeru Yoshida <syoshida@redhat.com>
To: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Tuomas Tynkkynen <tuomas@tuxera.com>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Shigeru Yoshida <syoshida@redhat.com>,
syzbot+6ed94e81a1492fe1d512@syzkaller.appspotmail.com,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH] 9p: don't ignore fatal signals during flush
Date: Sun, 22 Mar 2026 20:18:47 +0900 [thread overview]
Message-ID: <20260322111848.2837057-1-syoshida@redhat.com> (raw)
When a 9P RPC request is interrupted by a signal, p9_client_rpc() clears
TIF_SIGPENDING and attempts to flush the pending request by calling
p9_client_flush(). Since commit 9523feac272c switched the wait from
wait_event_interruptible() to wait_event_killable(), only SIGKILL can
interrupt the wait. However, the flush path also clears TIF_SIGPENDING,
which prevents subsequent wait_event_killable() calls from detecting the
already-pending SIGKILL. This makes the task unkillable.
When a coredump is initiated by another thread, zap_process() sends
SIGKILL to all threads. If a thread is stuck in the flush path as
described above, it never exits, and the dumper thread waits forever in
coredump_wait(), resulting in a hung task.
The same issue exists in p9_client_zc_rpc().
Skip the flush and the P9_TFLUSH retry loop when a fatal signal is
pending so that the task can exit promptly.
Fixes: 9523feac272c ("net/9p: Switch to wait_event_killable()")
Reported-by: syzbot+6ed94e81a1492fe1d512@syzkaller.appspotmail.com
Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
---
net/9p/client.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/net/9p/client.c b/net/9p/client.c
index f0dcf252af7e..28742f19041e 100644
--- a/net/9p/client.c
+++ b/net/9p/client.c
@@ -599,7 +599,7 @@ p9_client_rpc(struct p9_client *c, int8_t type, const char *fmt, ...)
smp_rmb();
if (err == -ERESTARTSYS && c->status == Connected &&
- type == P9_TFLUSH) {
+ type == P9_TFLUSH && !fatal_signal_pending(current)) {
sigpending = 1;
clear_thread_flag(TIF_SIGPENDING);
goto again;
@@ -609,7 +609,8 @@ p9_client_rpc(struct p9_client *c, int8_t type, const char *fmt, ...)
p9_debug(P9_DEBUG_ERROR, "req_status error %d\n", req->t_err);
err = req->t_err;
}
- if (err == -ERESTARTSYS && c->status == Connected) {
+ if (err == -ERESTARTSYS && c->status == Connected &&
+ !fatal_signal_pending(current)) {
p9_debug(P9_DEBUG_MUX, "flushing\n");
sigpending = 1;
clear_thread_flag(TIF_SIGPENDING);
@@ -694,7 +695,8 @@ static struct p9_req_t *p9_client_zc_rpc(struct p9_client *c, int8_t type,
p9_debug(P9_DEBUG_ERROR, "req_status error %d\n", req->t_err);
err = req->t_err;
}
- if (err == -ERESTARTSYS && c->status == Connected) {
+ if (err == -ERESTARTSYS && c->status == Connected &&
+ !fatal_signal_pending(current)) {
p9_debug(P9_DEBUG_MUX, "flushing\n");
sigpending = 1;
clear_thread_flag(TIF_SIGPENDING);
--
2.52.0
next reply other threads:[~2026-03-22 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 11:18 Shigeru Yoshida [this message]
2026-03-22 12:09 ` Dominique Martinet
2026-03-22 13:32 ` Dominique Martinet
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=20260322111848.2837057-1-syoshida@redhat.com \
--to=syoshida@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=syzbot+6ed94e81a1492fe1d512@syzkaller.appspotmail.com \
--cc=tuomas@tuxera.com \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®