mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+fa90fcaa28f5cd4b1fc1@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] possible deadlock in btrfs_read_chunk_tree
Date: Tue, 24 Jun 2025 07:27:04 -0700	[thread overview]
Message-ID: <685ab5b8.a00a0220.2e5631.007f.GAE@google.com> (raw)
In-Reply-To: <tencent_86C09604E922EC06CE1479EA6C582EC56C0A@qq.com>

Hello,

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

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

Tested on:

commit:         2ae2aaaf Add linux-next specific files for 20250624
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11b96b70580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=16ab4ce1313fe0b0
dashboard link: https://syzkaller.appspot.com/bug?extid=fa90fcaa28f5cd4b1fc1
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1198370c580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-06-24 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 13:11 syzbot
2025-06-24 13:56 ` Edward Adam Davis
2025-06-24 14:27   ` syzbot [this message]
2025-06-24 14:30 ` [PATCH next] btrfs: fix " Edward Adam Davis
2025-06-24 20:30   ` Qu Wenruo
2025-06-24 23:56     ` Hillf Danton
2025-06-25 10:49       ` Qu Wenruo
2025-06-25 12:40         ` Hillf Danton
2025-06-25 21:29           ` Qu Wenruo
2025-06-25 23:44             ` Hillf Danton
2025-06-29  4:27               ` Qu Wenruo
2025-06-29  4:59                 ` Hillf Danton
2025-06-29  5:05                   ` Qu Wenruo
2025-06-26  6:05 ` [syzbot] [btrfs?] possible " Qu Wenruo
2025-06-26  6:37   ` syzbot
2025-06-26  8:40     ` Qu Wenruo
2025-06-26 12:30       ` syzbot

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=685ab5b8.a00a0220.2e5631.007f.GAE@google.com \
    --to=syzbot+fa90fcaa28f5cd4b1fc1@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®