From: syzbot <syzbot+liste18b65911e42aaaf2e63@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, ericvh@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lucho@ionkov.net, syzkaller-bugs@googlegroups.com,
v9fs@lists.linux.dev
Subject: [syzbot] Monthly v9fs report (Apr 2024)
Date: Tue, 30 Apr 2024 00:12:28 -0700 [thread overview]
Message-ID: <000000000000b5c82b06174b1793@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, 0 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 28 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2768 Yes WARNING in v9fs_fid_get_acl
https://syzkaller.appspot.com/bug?extid=a83dc51a78f0f4cf20da
<2> 6 No WARNING: refcount bug in p9_req_put (3)
https://syzkaller.appspot.com/bug?extid=d99d2414db66171fccbb
<3> 5 Yes KMSAN: uninit-value in p9_client_rpc (2)
https://syzkaller.appspot.com/bug?extid=ff14db38f56329ef68df
---
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:[~2024-04-30 7:12 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=000000000000b5c82b06174b1793@google.com \
--to=syzbot+liste18b65911e42aaaf2e63@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.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 NNTP newsgroup(s).