public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: syzbot <syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com>
Cc: 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: Thu, 28 Apr 2022 01:02:10 +0200	[thread overview]
Message-ID: <20220427230210.GA6837@lst.de> (raw)
In-Reply-To: <000000000000d9f33705dda65450@google.com>

#syz test git://git.infradead.org/users/hch/misc.git btrfs-workqueue-fix

  reply	other threads:[~2022-04-27 23:04 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 [this message]
2022-04-28  5:05   ` syzbot
     [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=20220427230210.GA6837@lst.de \
    --to=hch@lst.de \
    --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=syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com \
    --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