All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+2665d678fffcc4608e18@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
	 linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	 quwenruo.btrfs@gmx.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in close_ctree
Date: Sat, 22 Mar 2025 23:21:03 -0700	[thread overview]
Message-ID: <67dfa84f.050a0220.31a16b.0056.GAE@google.com> (raw)
In-Reply-To: <03e95a73-6c8a-47b0-9b72-c1204118be47@gmx.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+2665d678fffcc4608e18@syzkaller.appspotmail.com
Tested-by: syzbot+2665d678fffcc4608e18@syzkaller.appspotmail.com

Tested on:

commit:         70a1072f btrfs: extract the main loop of btrfs_buffere..
git tree:       https://github.com/btrfs/linux.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12875c4c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d5d862b4e27dc0b3
dashboard link: https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2025-03-23  6:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  8:10 [syzbot] kernel BUG in close_ctree syzbot
2022-11-25 17:09 ` syzbot
2024-11-01  3:05   ` Julian Sun
2024-11-01  4:21     ` [syzbot] [btrfs?] " syzbot
2024-11-01  5:33       ` Julian Sun
2024-11-01  6:17         ` syzbot
2025-03-23  5:57 ` [syzbot] " Qu Wenruo
2025-03-23  6:21   ` syzbot [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=67dfa84f.050a0220.31a16b.0056.GAE@google.com \
    --to=syzbot+2665d678fffcc4608e18@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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.