From: syzbot <syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, hch@lst.de, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] general protection fault in btrfs_stop_all_workers
Date: Wed, 27 Apr 2022 22:05:13 -0700 [thread overview]
Message-ID: <000000000000fd713505ddafde13@google.com> (raw)
In-Reply-To: <20220427230210.GA6837@lst.de>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com
Tested on:
commit: ade4dbbb btrfs: don't call destroy_workqueue on NULL w..
git tree: git://git.infradead.org/users/hch/misc.git btrfs-workqueue-fix
kernel config: https://syzkaller.appspot.com/x/.config?x=17dad21e0facb5e6
dashboard link: https://syzkaller.appspot.com/bug?extid=a2c720e0f056114ea7c6
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2022-04-28 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:42 [syzbot] general protection fault in btrfs_stop_all_workers syzbot
2022-04-27 23:02 ` Christoph Hellwig
2022-04-28 5:05 ` syzbot [this message]
[not found] <20220427234836.3637-1-hdanton@sina.com>
2022-04-28 5:23 ` 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=000000000000fd713505ddafde13@google.com \
--to=syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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