All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d56e0d33caf7d1a02821@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, fdmanana@suse.com,
	johannes.thumshirn@wdc.com, josef@toxicpanda.com,
	linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in create_pending_snapshot
Date: Fri, 27 Oct 2023 04:11:06 -0700	[thread overview]
Message-ID: <000000000000a8f4b30608b0be9c@google.com> (raw)
In-Reply-To: <0000000000006cb13705ee3184f9@google.com>

syzbot suspects this issue was fixed by commit:

commit df9f278239046719c91aeb59ec0afb1a99ee8b2b
Author: Filipe Manana <fdmanana@suse.com>
Date:   Tue Jun 13 15:42:16 2023 +0000

    btrfs: do not BUG_ON on failure to get dir index for new snapshot

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1584c385680000
start commit:   0136d86b7852 Merge tag 'block-6.2-2023-02-03' of git://git..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ea620bd01d9130d
dashboard link: https://syzkaller.appspot.com/bug?extid=d56e0d33caf7d1a02821
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14657573480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16dd145d480000

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

#syz fix: btrfs: do not BUG_ON on failure to get dir index for new snapshot

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

  reply	other threads:[~2023-10-27 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  6:28 [syzbot] kernel BUG in create_pending_snapshot syzbot
2023-10-27 11:11 ` syzbot [this message]
2024-05-16 15:32   ` [syzbot] [btrfs?] " 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=000000000000a8f4b30608b0be9c@google.com \
    --to=syzbot+d56e0d33caf7d1a02821@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=fdmanana@suse.com \
    --cc=johannes.thumshirn@wdc.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 \
    /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.