All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
	xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Subject: Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems
Date: Thu, 4 Aug 2016 09:16:55 +1000	[thread overview]
Message-ID: <20160803231655.GY16044@dastard> (raw)
In-Reply-To: <20160803223713.GA22364@linux.intel.com>

On Wed, Aug 03, 2016 at 04:37:13PM -0600, Ross Zwisler wrote:
> On Wed, Aug 03, 2016 at 11:11:27AM -0600, Ross Zwisler wrote:
> > On Wed, Aug 03, 2016 at 10:33:54AM +1000, Dave Chinner wrote:
> > > Hi folks,
> > > 
> > > Just hit a reproducable hang in generic/361. Essentially this on
> > > a 8GB pmem device:
> > > 
> > > mkfs.xfs -f /dev/pmem1
> > > mount -o dax /dev/pmem1 /mnt/scratch
> > > xfs_io -f -c "truncate 1g" test.img
> > > losetup -f --show /mnt/scratch/test.img
> > > mkfs.xfs -f /dev/loop0
> > > 
> > > And the mkfs.xfs command hangs with a discard that never completes:
....
> > > This only reproduces when the underlying filesystem is mounted with
> > > -o dax, so there is a bad interaction with loop devices and DAX
> > > occurring somewhere. generic/361 is a recent test (committed june 14)
> > > so this probably hasn't actually been tested until now.
> > > 
> > > I haven't got time to look at this right now, hence the report.
> > 
> > Cool, thanks for the report.  I've reproduced this with linux/master, and the
> > test passes with v4.7.
> > 
> > Running a bisect...
> 
> This bisected to a commit to the block layer code.  I've sent a bug report to
> the author of the commit.

And the commit id is ...?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
	xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Subject: Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems
Date: Thu, 4 Aug 2016 09:16:55 +1000	[thread overview]
Message-ID: <20160803231655.GY16044@dastard> (raw)
In-Reply-To: <20160803223713.GA22364@linux.intel.com>

On Wed, Aug 03, 2016 at 04:37:13PM -0600, Ross Zwisler wrote:
> On Wed, Aug 03, 2016 at 11:11:27AM -0600, Ross Zwisler wrote:
> > On Wed, Aug 03, 2016 at 10:33:54AM +1000, Dave Chinner wrote:
> > > Hi folks,
> > > 
> > > Just hit a reproducable hang in generic/361. Essentially this on
> > > a 8GB pmem device:
> > > 
> > > mkfs.xfs -f /dev/pmem1
> > > mount -o dax /dev/pmem1 /mnt/scratch
> > > xfs_io -f -c "truncate 1g" test.img
> > > losetup -f --show /mnt/scratch/test.img
> > > mkfs.xfs -f /dev/loop0
> > > 
> > > And the mkfs.xfs command hangs with a discard that never completes:
....
> > > This only reproduces when the underlying filesystem is mounted with
> > > -o dax, so there is a bad interaction with loop devices and DAX
> > > occurring somewhere. generic/361 is a recent test (committed june 14)
> > > so this probably hasn't actually been tested until now.
> > > 
> > > I haven't got time to look at this right now, hence the report.
> > 
> > Cool, thanks for the report.  I've reproduced this with linux/master, and the
> > test passes with v4.7.
> > 
> > Running a bisect...
> 
> This bisected to a commit to the block layer code.  I've sent a bug report to
> the author of the commit.

And the commit id is ...?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>,
	xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Subject: Re: [4.8 hang] xfstests generic/361 hangs on dax enabled filesystems
Date: Thu, 4 Aug 2016 09:16:55 +1000	[thread overview]
Message-ID: <20160803231655.GY16044@dastard> (raw)
In-Reply-To: <20160803223713.GA22364@linux.intel.com>

On Wed, Aug 03, 2016 at 04:37:13PM -0600, Ross Zwisler wrote:
> On Wed, Aug 03, 2016 at 11:11:27AM -0600, Ross Zwisler wrote:
> > On Wed, Aug 03, 2016 at 10:33:54AM +1000, Dave Chinner wrote:
> > > Hi folks,
> > > 
> > > Just hit a reproducable hang in generic/361. Essentially this on
> > > a 8GB pmem device:
> > > 
> > > mkfs.xfs -f /dev/pmem1
> > > mount -o dax /dev/pmem1 /mnt/scratch
> > > xfs_io -f -c "truncate 1g" test.img
> > > losetup -f --show /mnt/scratch/test.img
> > > mkfs.xfs -f /dev/loop0
> > > 
> > > And the mkfs.xfs command hangs with a discard that never completes:
....
> > > This only reproduces when the underlying filesystem is mounted with
> > > -o dax, so there is a bad interaction with loop devices and DAX
> > > occurring somewhere. generic/361 is a recent test (committed june 14)
> > > so this probably hasn't actually been tested until now.
> > > 
> > > I haven't got time to look at this right now, hence the report.
> > 
> > Cool, thanks for the report.  I've reproduced this with linux/master, and the
> > test passes with v4.7.
> > 
> > Running a bisect...
> 
> This bisected to a commit to the block layer code.  I've sent a bug report to
> the author of the commit.

And the commit id is ...?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2016-08-03 23:17 UTC|newest]

Thread overview: 25+ 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:33 ` Dave Chinner
2016-08-03  0:33 ` Dave Chinner
2016-08-03  0:59 ` Dan Williams
2016-08-03  0:59   ` Dan Williams
2016-08-03  0:59   ` Dan Williams
2016-08-03 17:11 ` Ross Zwisler
2016-08-03 17:11   ` Ross Zwisler
2016-08-03 17:11   ` Ross Zwisler
2016-08-03 22:37   ` Ross Zwisler
2016-08-03 22:37     ` Ross Zwisler
2016-08-03 22:37     ` Ross Zwisler
2016-08-03 23:16     ` Dave Chinner [this message]
2016-08-03 23:16       ` Dave Chinner
2016-08-03 23:16       ` Dave Chinner
2016-08-04  2:52       ` Dan Williams
2016-08-04  2:52         ` Dan Williams
2016-08-04  2:52         ` Dan Williams
2016-08-04 15:48 ` Christoph Hellwig
2016-08-04 15:48   ` Christoph Hellwig
     [not found]   ` <20160804154805.GA24025-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-08-04 18:46     ` Ross Zwisler
2016-08-04 18:46       ` Ross Zwisler
2016-08-04 18:46       ` Ross Zwisler
2016-08-04 18:54       ` 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=20160803231655.GY16044@dastard \
    --to=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=ross.zwisler@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.