All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+afdee14f9fd3d20448e7@syzkaller.appspotmail.com>
To: chris@chrisdown.name, clm@fb.com, dsterba@suse.com,
	josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, xiaoshoukui@gmail.com,
	xiaoshoukui@ruijie.com.cn
Subject: Re: [syzbot] [btrfs?] kernel BUG in btrfs_ioctl_add_dev
Date: Tue, 06 Jun 2023 02:55:38 -0700	[thread overview]
Message-ID: <00000000000073fb7305fd730525@google.com> (raw)
In-Reply-To: <00000000000002eb8105f51cfa96@google.com>

syzbot suspects this issue was fixed by commit:

commit ac868bc9d136cde6e3eb5de77019a63d57a540ff
Author: xiaoshoukui <xiaoshoukui@gmail.com>
Date:   Thu Apr 13 09:55:07 2023 +0000

    btrfs: fix assertion of exclop condition when starting balance

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12bdc3a3280000
start commit:   04a357b1f6f0 Merge tag 'mips_6.3_1' of git://git.kernel.or..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=f763d89e26d3d4c4
dashboard link: https://syzkaller.appspot.com/bug?extid=afdee14f9fd3d20448e7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11f043b0c80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15d2ea9cc80000

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

#syz fix: btrfs: fix assertion of exclop condition when starting balance

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

  reply	other threads:[~2023-06-06  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  7:54 [syzbot] [btrfs?] kernel BUG in btrfs_ioctl_add_dev syzbot
2023-06-06  9:55 ` syzbot [this message]
2023-06-06 14:03   ` David Sterba

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=00000000000073fb7305fd730525@google.com \
    --to=syzbot+afdee14f9fd3d20448e7@syzkaller.appspotmail.com \
    --cc=chris@chrisdown.name \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiaoshoukui@gmail.com \
    --cc=xiaoshoukui@ruijie.com.cn \
    /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.