mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Hillf Danton <hdanton@sina.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Edward Adam Davis <eadavis@qq.com>,
	syzbot+fa90fcaa28f5cd4b1fc1@syzkaller.appspotmail.com,
	clm@fb.com, josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH next] btrfs: fix deadlock in btrfs_read_chunk_tree
Date: Sun, 29 Jun 2025 14:35:28 +0930	[thread overview]
Message-ID: <66c06601-94ff-47df-a951-157a1315aa99@suse.com> (raw)
In-Reply-To: <20250629050000.2069-1-hdanton@sina.com>



在 2025/6/29 14:29, Hillf Danton 写道:
> On Sun, 29 Jun 2025 13:57:43 +0930 Qu Wenruo wrote:
>> 在 2025/6/26 09:14, Hillf Danton 写道:
>>> Fine, feel free to show us the Tested-by syzbot gave you.
>>>
>> Here you go:
>>
>> https://lore.kernel.org/linux-btrfs/685d3d4c.050a0220.2303ee.01ca.GAE@google.com/
>>
>> That's based on a branch with extra patches though.
>>
> Thanks, feel free to spin with the Tested-by tag added.
> 

Normally we only add reported-by/tested-by from syzbot when the 
offending commit is already upstreamed.

Since the series is only in linux-next, not even in btrfs for-next 
branch, I believe no tags will be added in this case.

Thanks,
Qu


  reply	other threads:[~2025-06-29  5:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 13:11 [syzbot] [btrfs?] possible " syzbot
2025-06-24 13:56 ` Edward Adam Davis
2025-06-24 14:27   ` syzbot
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 [this message]
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=66c06601-94ff-47df-a951-157a1315aa99@suse.com \
    --to=wqu@suse.com \
    --cc=clm@fb.com \
    --cc=eadavis@qq.com \
    --cc=hdanton@sina.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=syzbot+fa90fcaa28f5cd4b1fc1@syzkaller.appspotmail.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 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®