From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+3abaeed5039cc1c49c7c@syzkaller.appspotmail.com>,
axboe@kernel.dk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in chown_common
Date: Thu, 18 Jan 2024 15:40:02 +0100 [thread overview]
Message-ID: <20240118-badeverbot-gemustert-e87bd2a23bfc@brauner> (raw)
In-Reply-To: <20240117165236.kcmlvjedoae6yd76@quack3>
On Wed, Jan 17, 2024 at 05:52:36PM +0100, Jan Kara wrote:
> On Wed 17-01-24 08:20:06, syzbot wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit 6f861765464f43a71462d52026fbddfc858239a5
> > Author: Jan Kara <jack@suse.cz>
> > Date: Wed Nov 1 17:43:10 2023 +0000
> >
> > fs: Block writes to mounted block devices
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ecbc83e80000
> > start commit: 2bca25eaeba6 Merge tag 'spi-v6.1' of git://git.kernel.org/..
> > git tree: upstream
> > kernel config: https://syzkaller.appspot.com/x/.config?x=9df203be43a870b5
> > dashboard link: https://syzkaller.appspot.com/bug?extid=3abaeed5039cc1c49c7c
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1539e7b8880000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c6cb32880000
> >
> > If the result looks correct, please mark the issue as fixed by replying with:
>
> Makes sense:
>
> #syz fix: fs: Block writes to mounted block devices
I remember once trying to chase that bug down and being very confused.
prev parent reply other threads:[~2024-01-18 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 3:09 [syzbot] possible deadlock in chown_common syzbot
2024-01-17 16:20 ` [syzbot] [reiserfs?] " syzbot
2024-01-17 16:52 ` Jan Kara
2024-01-18 14:40 ` 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=20240118-badeverbot-gemustert-e87bd2a23bfc@brauner \
--to=brauner@kernel.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzbot+3abaeed5039cc1c49c7c@syzkaller.appspotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.