From: syzbot <syzbot+d1e76d963f757db40f91@syzkaller.appspotmail.com>
To: Dai.Ngo@oracle.com, chuck.lever@oracle.com, dai.ngo@oracle.com,
jlayton@kernel.org, kolga@netapp.com,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
lorenzo@kernel.org, neilb@suse.de,
syzkaller-bugs@googlegroups.com, tom@talpey.com
Subject: Re: [syzbot] [nfs?] INFO: task hung in nfsd_nl_listener_set_doit
Date: Sun, 04 Aug 2024 16:16:02 -0700 [thread overview]
Message-ID: <00000000000076525c061ee3be52@google.com> (raw)
In-Reply-To: <0000000000004385ec06198753f8@google.com>
syzbot has bisected this issue to:
commit 16a471177496c8e04a9793812c187a2c1a2192fa
Author: Lorenzo Bianconi <lorenzo@kernel.org>
Date: Tue Apr 23 13:25:44 2024 +0000
NFSD: add listener-{set,get} netlink command
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16af38d3980000
start commit: ee78a17615ad Add linux-next specific files for 20240606
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15af38d3980000
console output: https://syzkaller.appspot.com/x/log.txt?x=11af38d3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a8c69ee180de0793
dashboard link: https://syzkaller.appspot.com/bug?extid=d1e76d963f757db40f91
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173f2eac980000
Reported-by: syzbot+d1e76d963f757db40f91@syzkaller.appspotmail.com
Fixes: 16a471177496 ("NFSD: add listener-{set,get} netlink command")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-04 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 17:54 [syzbot] [nfs?] INFO: task hung in nfsd_nl_listener_set_doit syzbot
2024-05-28 18:10 ` Jeff Layton
2024-08-04 23:16 ` syzbot [this message]
2024-08-31 18:22 ` syzbot
2024-09-01 4:35 ` Edward Adam Davis
2024-09-01 4:51 ` syzbot
2024-09-01 6:25 ` Edward Adam Davis
2024-09-01 6:50 ` syzbot
2024-09-02 1:57 ` NeilBrown
2024-09-04 14:23 ` Chuck Lever
2024-09-04 14:36 ` Jeff Layton
2024-10-09 20:26 ` Jeff Layton
2024-10-11 18:18 ` Chuck Lever III
2024-10-11 19:15 ` Jeff Layton
2024-10-11 21:08 ` NeilBrown
2024-10-11 21:13 ` Chuck Lever III
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=00000000000076525c061ee3be52@google.com \
--to=syzbot+d1e76d963f757db40f91@syzkaller.appspotmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=neilb@suse.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@talpey.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