From: syzbot <syzbot+a531d1b1fb0fa2a75a73@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] fuse: allow fatal signals to interrupt forced requests
Date: Fri, 24 Jul 2026 03:26:40 -0700 [thread overview]
Message-ID: <6a633de0.dde6c935.cf6c8.0019.GAE@google.com> (raw)
In-Reply-To: <6a32f564.9e11d3f7.246028.0002.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] fuse: allow fatal signals to interrupt forced requests
Author: jeffinphilip14@gmail.com
#syz test
Signed-off-by: Jeffin Philip <jeffinphilip14@gmail.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 5763a7cd3b37..837f3cec3c86 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -714,7 +714,7 @@ static void request_wait_answer(struct fuse_req *req)
queue_interrupt(req);
}
- if (!test_bit(FR_FORCE, &req->flags)) {
+ if (!test_bit(FR_FORCE, &req->flags) || unlikely(fatal_signal_pending(current))) {
bool removed;
/* Only fatal signals may interrupt this */
--
2.55.0
next prev parent reply other threads:[~2026-07-24 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 19:28 [syzbot] [fuse?] INFO: task hung in fuse_chan_send syzbot
2026-07-24 9:59 ` Forwarded: Patch test syzbot
2026-07-24 10:02 ` Forwarded: Testv2 syzbot
2026-07-24 10:14 ` Forwarded: [PATCH] fuse: allow fatal signals to interrupt forced requests syzbot
2026-07-24 10:26 ` syzbot [this message]
2026-07-24 10:59 ` syzbot
2026-07-24 12:52 ` Forwarded: syzbot
2026-07-24 13:30 ` Forwarded: [PATCH] fuse: allow fatal signals to interrupt forced requests syzbot
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=6a633de0.dde6c935.cf6c8.0019.GAE@google.com \
--to=syzbot+a531d1b1fb0fa2a75a73@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome