From: Dave Chinner <david@fromorbit.com>
To: syzbot <syzbot+3f083e9e08b726fcfba2@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, chandan.babu@oracle.com,
djwong@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin
Date: Thu, 8 Feb 2024 08:15:26 +1100 [thread overview]
Message-ID: <ZcPy7sm6SujCXwXv@dread.disaster.area> (raw)
In-Reply-To: <0000000000006f69c90610a8edb3@google.com>
On Mon, Feb 05, 2024 at 01:13:04PM -0800, 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=176f2d7be80000
> start commit: d2980d8d8265 Merge tag 'mm-nonmm-stable-2023-02-20-15-29' ..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=471a946f0dd5764c
> dashboard link: https://syzkaller.appspot.com/bug?extid=3f083e9e08b726fcfba2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a077d8c80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d91c74c80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: Block writes to mounted block devices
No, not even close.
-Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-02-07 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 1:30 [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin syzbot
2024-02-05 21:13 ` syzbot
2024-02-07 21:15 ` Dave Chinner [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=ZcPy7sm6SujCXwXv@dread.disaster.area \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+3f083e9e08b726fcfba2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox