From: syzbot <syzbot+list6e31de9aa6d237da5d04@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, ericvh@kernel.org,
linux-kernel@vger.kernel.org, lucho@ionkov.net,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev
Subject: [syzbot] Monthly v9fs report (Mar 2025)
Date: Tue, 04 Mar 2025 07:15:20 -0800 [thread overview]
Message-ID: <67c71908.050a0220.15b4b9.0011.GAE@google.com> (raw)
Hello v9fs maintainers/developers,
This is a 31-day syzbot report for the v9fs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/v9fs
During the period, 2 new issues were detected and 0 were fixed.
In total, 13 issues are still open and 34 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1131 Yes WARNING in __alloc_frozen_pages_noprof
https://syzkaller.appspot.com/bug?extid=03fb58296859d8dbab4d
<2> 40 Yes WARNING: refcount bug in p9_req_put (3)
https://syzkaller.appspot.com/bug?extid=d99d2414db66171fccbb
<3> 12 No BUG: corrupted list in p9_fd_cancelled (3)
https://syzkaller.appspot.com/bug?extid=15a08eabe3d3838fb641
---
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-03-04 15:15 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=67c71908.050a0220.15b4b9.0011.GAE@google.com \
--to=syzbot+list6e31de9aa6d237da5d04@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).