From: syzbot <syzbot+list316c1d421205de40320d@syzkaller.appspotmail.com>
To: amir73il@gmail.com, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly overlayfs report (Jun 2024)
Date: Sat, 15 Jun 2024 10:49:20 -0700 [thread overview]
Message-ID: <00000000000011db0b061af15a3c@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, 1 new issues were detected and 0 were fixed.
In total, 3 issues are still open and 26 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 21 Yes BUG: unable to handle kernel NULL pointer dereference in __lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=94891a5155abdf6821b7
<2> 7 No possible deadlock in ovl_copy_up_start (4)
https://syzkaller.appspot.com/bug?extid=6d34d0b636fea8b593eb
<3> 4 No KASAN: slab-use-after-free Read in ovl_dentry_update_reval
https://syzkaller.appspot.com/bug?extid=316db8a1191938280eb6
---
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-06-15 17:49 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=00000000000011db0b061af15a3c@google.com \
--to=syzbot+list316c1d421205de40320d@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--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