From: Dan Williams <dan.j.williams@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Murphy Zhou <jencce.kernel@gmail.com>,
Linux NVDIMM <nvdimm@lists.linux.dev>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [regression] fs dax xfstests panic
Date: Mon, 27 Sep 2021 16:14:48 -0700 [thread overview]
Message-ID: <CAPcyv4j1jSSQNBw991_PPu72Q3he=ctYpaLTSh3AjbJ5nA3UVQ@mail.gmail.com> (raw)
In-Reply-To: <20210927230259.GA2706839@magnolia>
On Mon, Sep 27, 2021 at 4:03 PM Darrick J. Wong <djwong@kernel.org> wrote:
>
> On Mon, Sep 27, 2021 at 01:51:16PM +0200, Christoph Hellwig wrote:
> > On Mon, Sep 27, 2021 at 02:17:47PM +0800, Murphy Zhou wrote:
> > > Hi folks,
> > >
> > > Since this commit:
> > >
> > > commit edb0872f44ec9976ea6d052cb4b93cd2d23ac2ba
> > > Author: Christoph Hellwig <hch@lst.de>
> > > Date: Mon Aug 9 16:17:43 2021 +0200
> > >
> > > block: move the bdi from the request_queue to the gendisk
> > >
> > >
> > > Looping xfstests generic/108 or xfs/279 on mountpoints with fsdax
> > > enabled can lead to panic like this:
> >
> > Does this still happen with this series:
> >
> > https://lore.kernel.org/linux-block/20210922172222.2453343-1-hch@lst.de/T/#m8dc646a4dfc40f443227da6bb1c77d9daec524db
> >
> > ?
>
> My test machinse all hit this when writeback throttling is enabled, so
>
> Tested-by: Darrick J. Wong <djwong@kernel.org>
Thanks Darrick, I've added that.
next prev parent reply other threads:[~2021-09-27 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 6:17 [regression] fs dax xfstests panic Murphy Zhou
2021-09-27 11:51 ` Christoph Hellwig
2021-09-27 23:02 ` Darrick J. Wong
2021-09-27 23:14 ` Dan Williams [this message]
2021-09-28 4:34 ` Christoph Hellwig
2021-09-28 5:16 ` Darrick J. Wong
2021-09-28 5:17 ` Christoph Hellwig
2021-09-28 5:20 ` Darrick J. Wong
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='CAPcyv4j1jSSQNBw991_PPu72Q3he=ctYpaLTSh3AjbJ5nA3UVQ@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jencce.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).