From: syzbot <syzbot+4e21d5f67b886a692b55@syzkaller.appspotmail.com>
To: abbotti@mev.co.uk, axboe@kernel.dk, brauner@kernel.org,
gregkh@linuxfoundation.org, hdanton@sina.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, lizhi.xu@windriver.com,
mchehab@kernel.org, standback@126.com, superman.xpt@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] BUG: corrupted list in remove_wait_queue (2)
Date: Thu, 15 Jan 2026 15:32:05 -0800 [thread overview]
Message-ID: <696978f5.050a0220.58bed.0030.GAE@google.com> (raw)
In-Reply-To: <67917ed8.050a0220.15cac.02eb.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 35b6fc51c666fc96355be5cd633ed0fe4ccf68b2
Author: Ian Abbott <abbotti@mev.co.uk>
Date: Tue Jul 22 15:53:16 2025 +0000
comedi: fix race between polling and detaching
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d49dfc580000
start commit: 038d61fd6422 Linux 6.16
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=515ec0b49771bcd1
dashboard link: https://syzkaller.appspot.com/bug?extid=4e21d5f67b886a692b55
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fbbcf0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11034aa2580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: comedi: fix race between polling and detaching
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-01-15 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67917ed8.050a0220.15cac.02eb.GAE@google.com>
2025-07-07 9:30 ` [syzbot] [fs?] BUG: corrupted list in remove_wait_queue (2) syzbot
2026-01-15 23:32 ` syzbot [this message]
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=696978f5.050a0220.58bed.0030.GAE@google.com \
--to=syzbot+4e21d5f67b886a692b55@syzkaller.appspotmail.com \
--cc=abbotti@mev.co.uk \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=mchehab@kernel.org \
--cc=standback@126.com \
--cc=superman.xpt@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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