From: syzbot <syzbot+63ab1a905aebbf410bb7@syzkaller.appspotmail.com>
To: brauner@kernel.org, gregkh@linuxfoundation.org,
isdn@linux-pingi.de, jack@suse.cz, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [kernfs?] INFO: task hung in eventpoll_release_file (2)
Date: Sat, 19 Oct 2024 15:03:02 -0700 [thread overview]
Message-ID: <67142c96.050a0220.10f4f4.0021.GAE@google.com> (raw)
In-Reply-To: <00000000000087e83e061dd271bd@google.com>
syzbot suspects this issue was fixed by commit:
commit 0023d340ba86cfe50b935829a73adea57ec2c629
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Tue Sep 10 14:22:36 2024 +0000
Bluetooth: CMTP: Mark BT_CMTP as DEPRECATED
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1594c430580000
start commit: b31c44928842 Merge tag 'linux_kselftest-kunit-fixes-6.11-r..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=58a85aa6925a8b78
dashboard link: https://syzkaller.appspot.com/bug?extid=63ab1a905aebbf410bb7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10662bc7980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137bba00580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: CMTP: Mark BT_CMTP as DEPRECATED
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-19 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 9:12 [syzbot] [kernfs?] INFO: task hung in eventpoll_release_file (2) syzbot
2024-09-07 17:53 ` syzbot
2024-10-19 22:03 ` 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=67142c96.050a0220.10f4f4.0021.GAE@google.com \
--to=syzbot+63ab1a905aebbf410bb7@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=isdn@linux-pingi.de \
--cc=jack@suse.cz \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--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