From: syzbot <syzbot+lista7343adf220a77c2e87e@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly overlayfs report (Jul 2023)
Date: Mon, 24 Jul 2023 01:31:56 -0700 [thread overview]
Message-ID: <0000000000008e4e370601377210@google.com> (raw)
Hello overlayfs maintainers/developers,
This is a 31-day syzbot report for the overlayfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/overlayfs
During the period, 3 new issues were detected and 1 were fixed.
In total, 7 issues are still open and 18 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 727 Yes possible deadlock in mnt_want_write (2)
https://syzkaller.appspot.com/bug?extid=b42fe626038981fb7bfa
<2> 50 No general protection fault in d_path
https://syzkaller.appspot.com/bug?extid=a67fc5321ffb4b311c98
<3> 5 No possible deadlock in seq_read_iter (2)
https://syzkaller.appspot.com/bug?extid=da4f9f61f96525c62cc7
---
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:[~2023-07-24 8:32 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=0000000000008e4e370601377210@google.com \
--to=syzbot+lista7343adf220a77c2e87e@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).