From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+e25ef173c0758ea764de@syzkaller.appspotmail.com>
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING in stashed_dentry_prune (2)
Date: Fri, 10 May 2024 13:34:39 +0200 [thread overview]
Message-ID: <20240510-blechnapf-bienen-b9b049b1bb28@brauner> (raw)
In-Reply-To: <000000000000decb7906180aae28@google.com>
On Thu, May 09, 2024 at 12:47:02PM -0700, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 2558e3b23112adb82a558bab616890a790a38bc6
So this sent me on a wild goose chase. In the last couple of weeks I got
multiple reports from syzbot (3-4, I think) that all reported bugs
reproduced against trees that were way behind mainline. So in this example:
#syz fix: pidfs: remove config option
prev parent reply other threads:[~2024-05-10 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 9:47 [syzbot] [fs?] WARNING in stashed_dentry_prune (2) syzbot
2024-05-09 19:47 ` syzbot
2024-05-10 11:34 ` Christian Brauner [this message]
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=20240510-blechnapf-bienen-b9b049b1bb28@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+e25ef173c0758ea764de@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).