From: David Sterba <dsterba@suse.cz>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: btrfs crash in kobject_del while running xfstest
Date: Tue, 11 Aug 2020 16:02:11 +0200 [thread overview]
Message-ID: <20200811140211.GQ2026@twin.jikos.cz> (raw)
In-Reply-To: <2a3eb48d-6ca1-61c6-20cf-ba2fbda21f45@nvidia.com>
On Tue, Aug 11, 2020 at 04:19:47AM -0700, John Hubbard wrote:
> Somehow the copy-paste of Chris Mason's name failed (user error
> on my end), sorry about that Chris!
>
> On 8/11/20 4:17 AM, John Hubbard wrote:
> > Hi,
> >
> > Here's an early warning of a possible problem.
> >
> > I'm seeing a new btrfs crash when running xfstests, as of
> > 00e4db51259a5f936fec1424b884f029479d3981 ("Merge tag
> > 'perf-tools-2020-08-10' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux") in linux.git.
> >
> > This doesn't crash in v5.8, so I attempted to bisect, but ended up with
> > the net-next merge commit as the offending one: commit
> > 47ec5303d73ea344e84f46660fff693c57641386 ("Merge
> > git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next"), which
> > doesn't really help because it's 2088 files changed, of course.
Thanks for the report, it's already known and patch is on the way to
Linus' tree (ETA before rc1). You can apply
https://lore.kernel.org/linux-btrfs/20200803062011.17291-1-wqu@suse.com/
locally.
prev parent reply other threads:[~2020-08-11 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200e5b49-5c51-bbe5-de93-c6bd6339bb7f@nvidia.com>
2020-08-11 11:19 ` btrfs crash in kobject_del while running xfstest John Hubbard
2020-08-11 14:02 ` David Sterba [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=20200811140211.GQ2026@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jhubbard@nvidia.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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