From: Christian Brauner <brauner@kernel.org>
To: syzbot <syzbot+3acccbed6f1454bf337c@syzkaller.appspotmail.com>
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING: ODEBUG bug in bdev_super_lock (2)
Date: Thu, 18 Apr 2024 13:27:42 +0200 [thread overview]
Message-ID: <20240418-emsig-abgehackt-b5c21d3a3e78@brauner> (raw)
In-Reply-To: <0000000000006249a406164ec138@google.com>
On Wed, Apr 17, 2024 at 11:09:27AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
The cause of this bug has long been fixed upstream. The commit listed
here where this is tested on is prior to that fix.
> git tree: upstream
#syz fix: fs,block: yield devices early
prev parent reply other threads:[~2024-04-18 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:09 [syzbot] [fs?] WARNING: ODEBUG bug in bdev_super_lock (2) syzbot
2024-04-18 11:27 ` 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=20240418-emsig-abgehackt-b5c21d3a3e78@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3acccbed6f1454bf337c@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 NNTP newsgroup(s).