linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org, linux-nvdimm@ml01.01.org
Subject: Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems
Date: Thu, 4 Aug 2016 08:48:05 -0700	[thread overview]
Message-ID: <20160804154805.GA24025@infradead.org> (raw)
In-Reply-To: <20160803003354.GP16044@dastard>

Just send a fix that you're Cc'ed on.  But now xfs/049 hangs, although
only on pmem devices, loop on non-pmem seems to be fine.  4.7 was fine
as well.

  parent reply	other threads:[~2016-08-04 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  0:33 [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems Dave Chinner
2016-08-03  0:59 ` Dan Williams
2016-08-03 17:11 ` Ross Zwisler
2016-08-03 22:37   ` Ross Zwisler
2016-08-03 23:16     ` Dave Chinner
2016-08-04  2:52       ` Dan Williams
2016-08-04 15:48 ` Christoph Hellwig [this message]
2016-08-04 18:46   ` Ross Zwisler
2016-08-04 18:54     ` Ross Zwisler

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=20160804154805.GA24025@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).