From: syzbot <syzbot+90392eaed540afcc8fc3@syzkaller.appspotmail.com>
To: amir73il@gmail.com, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] [overlayfs?] BUG: unable to handle kernel paging request in take_dentry_name_snapshot
Date: Sun, 30 Jul 2023 07:34:37 -0700 [thread overview]
Message-ID: <000000000000a7178a0601b5366f@google.com> (raw)
In-Reply-To: <0000000000003b7fee05eec392a8@google.com>
syzbot suspects this issue was fixed by commit:
commit 1784fbc2ed9c888ea4e895f30a53207ed7ee8208
Author: Christian Brauner <brauner@kernel.org>
Date: Fri Jun 16 12:53:58 2023 +0000
ovl: port to new mount api
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12561bd9a80000
start commit: 8395ae05cb5a Merge tag 'scsi-misc' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=85327a149d5f50f
dashboard link: https://syzkaller.appspot.com/bug?extid=90392eaed540afcc8fc3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16199460480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1797f274480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ovl: port to new mount api
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-30 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:43 [syzbot] BUG: unable to handle kernel paging request in take_dentry_name_snapshot syzbot
2022-12-23 5:32 ` [syzbot] [reiserfs?] [fat?] " syzbot
2023-07-30 14:34 ` syzbot [this message]
2023-10-04 8:35 ` [syzbot] [reiserfs?] [overlayfs?] " Amir Goldstein
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=000000000000a7178a0601b5366f@google.com \
--to=syzbot+90392eaed540afcc8fc3@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=reiserfs-devel@vger.kernel.org \
--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).