linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+53b443b5c64221ee8bad@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, chandan.babu@oracle.com,
	 dchinner@redhat.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?] WARNING in xfs_bmapi_convert_delalloc
Date: Tue, 06 Feb 2024 22:02:05 -0800	[thread overview]
Message-ID: <00000000000032f84a0610c46f89@google.com> (raw)
In-Reply-To: <0000000000001bebd305ee5cd30e@google.com>

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=12b0ad7be80000
start commit:   e8c127b05766 Merge tag 'net-6.6-rc6' of git://git.kernel.o..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=11e478e28144788c
dashboard link: https://syzkaller.appspot.com/bug?extid=53b443b5c64221ee8bad
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14a6f291680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=116bc355680000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs: Block writes to mounted block devices

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2024-02-07  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 10:08 [syzbot] WARNING in xfs_bmapi_convert_delalloc syzbot
2022-12-23 10:15 ` [syzbot] [xfs?] " syzbot
2024-02-07  6:02 ` syzbot [this message]
2024-02-07 21:17   ` Dave Chinner
2024-02-07 22:18     ` Jan Kara

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=00000000000032f84a0610c46f89@google.com \
    --to=syzbot+53b443b5c64221ee8bad@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.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=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).