linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+listf458cf6e943ee253729f@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
Date: Wed, 05 Apr 2023 01:55:47 -0700	[thread overview]
Message-ID: <00000000000047b8d005f892f5f0@google.com> (raw)

Hello overlayfs maintainers/developers,

This is a 30-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, 0 new issues were detected and 0 were fixed.
In total, 11 issues are still open and 17 have been fixed so far.

Some of the still happening issues:

Crashes Repro Title
785     Yes   possible deadlock in ovl_maybe_copy_up
              https://syzkaller.appspot.com/bug?extid=c18f2f6a7b08c51e3025
442     Yes   possible deadlock in mnt_want_write (2)
              https://syzkaller.appspot.com/bug?extid=b42fe626038981fb7bfa
24      Yes   BUG: unable to handle kernel paging request in take_dentry_name_snapshot
              https://syzkaller.appspot.com/bug?extid=90392eaed540afcc8fc3
11      Yes   WARNING: locking bug in take_dentry_name_snapshot
              https://syzkaller.appspot.com/bug?extid=5a195884ee3ad761db4e

---
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.

                 reply	other threads:[~2023-04-05  8:55 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=00000000000047b8d005f892f5f0@google.com \
    --to=syzbot+listf458cf6e943ee253729f@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 NNTP newsgroup(s).