From: syzbot <syzbot+listdc1ca7bb566f225a8ae2@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nfs report (Jul 2025)
Date: Fri, 04 Jul 2025 05:38:24 -0700 [thread overview]
Message-ID: <6867cb40.a70a0220.29cf51.001b.GAE@google.com> (raw)
Hello nfs maintainers/developers,
This is a 31-day syzbot report for the nfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/nfs
During the period, 0 new issues were detected and 1 were fixed.
In total, 9 issues are still open and 17 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 20778 Yes INFO: task hung in nfsd_nl_listener_set_doit
https://syzkaller.appspot.com/bug?extid=d1e76d963f757db40f91
<2> 2447 No INFO: task hung in nfsd_umount
https://syzkaller.appspot.com/bug?extid=b568ba42c85a332a88ee
<3> 939 No INFO: task hung in nfsd_nl_version_get_doit
https://syzkaller.appspot.com/bug?extid=41bc60511c2884783c27
<4> 827 No INFO: task hung in nfsd_nl_threads_get_doit
https://syzkaller.appspot.com/bug?extid=c0831b61d6ade1e2d098
<5> 817 No INFO: task hung in nfsd_nl_rpc_status_get_dumpit
https://syzkaller.appspot.com/bug?extid=68f089d6e18e8b1d41eb
<6> 804 No INFO: task hung in nfsd_nl_listener_get_doit
https://syzkaller.appspot.com/bug?extid=4207adf14e7c0981d28d
<7> 324 Yes INFO: task hung in nfsd_nl_threads_set_doit
https://syzkaller.appspot.com/bug?extid=e7baeb70aa00c22ed45e
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-07-04 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6867cb40.a70a0220.29cf51.001b.GAE@google.com \
--to=syzbot+listdc1ca7bb566f225a8ae2@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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