From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+eede1fb91fb15bbbd5f2@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] INFO: task hung in fuse_conn_destroy (2)
Date: Sun, 19 Apr 2026 11:51:51 +0800 [thread overview]
Message-ID: <tencent_44960DA29223DDF85DB9195ACFD28D87A507@qq.com> (raw)
In-Reply-To: <69e1934c.a70a0220.7229.0010.GAE@google.com>
#syz test
diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c
index 25c5c853a791..7c130656c4f6 100644
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -2291,6 +2291,9 @@ static long fuse_dev_ioctl_clone(struct file *file, __u32 __user *argp)
return -ENOMEM;
new_fud = fuse_file_to_fud(file);
+ if (fuse_dev_chan_get(new_fud))
+ return -EINVAL;
+
if (!fuse_dev_install_with_pq(new_fud, fud->chan, pq))
return -EINVAL;
next prev parent reply other threads:[~2026-04-19 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 1:56 [syzbot] [fuse?] INFO: task hung in fuse_conn_destroy (2) syzbot
2026-04-19 3:51 ` Edward Adam Davis [this message]
2026-04-19 5:15 ` syzbot
2026-04-19 5:26 ` [PATCH next] fuse: avoid using the same file descriptor when cloning Edward Adam Davis
2026-04-20 10:52 ` Miklos Szeredi
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=tencent_44960DA29223DDF85DB9195ACFD28D87A507@qq.com \
--to=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+eede1fb91fb15bbbd5f2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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