From: Ze Tan <tanze@kylinos.cn>
To: ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
linux_oss@crudebyte.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, v9fs@lists.linux.dev,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tanze@kylinos.cn
Subject: [PATCH v2 0/3] net/9p: safely abort fd RPCs on fatal signals
Date: Thu, 16 Jul 2026 15:30:48 +0800 [thread overview]
Message-ID: <cover.1784186316.git.tanze@kylinos.cn> (raw)
Hi,
This series fixes a hung task reported by Syzkaller when a thread blocked
in a 9p fd RPC receives a fatal signal while another thread in the same
group is waiting in coredump_wait(). The interrupted RPC currently enters
the TFLUSH path and can wait indefinitely if the 9p server is no longer
responding, preventing the thread from exiting and the coredump from
completing.
Ze Tan (3):
net/9p: handle replies racing with interrupted RPCs
net/9p: prepare fd transports for asynchronous aborts
net/9p: abort interrupted fd RPCs on fatal signals
include/net/9p/client.h | 3 +++
include/net/9p/transport.h | 4 ++++
net/9p/client.c | 35 +++++++++++++++++++++++++++++++++++
net/9p/trans_fd.c | 10 +++++++++-
4 files changed, 51 insertions(+), 1 deletion(-)
base-commit: 58717b2a1365d06c8c64b72aa948541b53fe31eb
--
2.43.0
next reply other threads:[~2026-07-16 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 7:30 Ze Tan [this message]
2026-07-16 7:30 ` [PATCH v2 1/3] net/9p: handle replies racing with interrupted RPCs Ze Tan
2026-07-16 7:30 ` [PATCH v2 2/3] net/9p: prepare fd transports for asynchronous aborts Ze Tan
2026-07-16 7:30 ` [PATCH v2 3/3] net/9p: abort interrupted fd RPCs on fatal signals Ze Tan
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=cover.1784186316.git.tanze@kylinos.cn \
--to=tanze@kylinos.cn \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.