All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: fstests@vger.kernel.org, Jan Kara <jack@suse.cz>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-nvdimm@lists.01.org, Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [fstests PATCH v2] xfs: add regression test for DAX mount option usage
Date: Thu, 14 Sep 2017 14:57:41 +0800	[thread overview]
Message-ID: <20170914065741.GH8034@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170911200103.28226-1-ross.zwisler@linux.intel.com>

Hi Ross,

On Mon, Sep 11, 2017 at 02:01:03PM -0600, Ross Zwisler wrote:
> This adds a regression test for the following kernel patch:
> 
>   xfs: always use DAX if mount option is used
> 
> This test will also pass with kernel v4.14-rc1 and beyond because the XFS
> DAX I/O mount option has been disabled (but not removed), so the
> "chattr -x" to turn off DAX doesn't actually do anything.
> 
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> ---
> 
> Changes since v1:
>  - Use perf instead of tracepoints to detect whether DAX is used. (Dan)

Thanks for the test! But I agreed with Dave here, it doesn't seem like a
good idea to depend on the kernel tracepoints in a test, but I can't
think of a better solution either, so I didn't get to this patch
earlier..

Before XFS disabled the ability to switch on & off per-inode DAX flag,
the x flag was only shown after an explicit 'chattr +x', even if XFS was
mounted with dax option, e.g.

# mkfs -t xfs -f /dev/ram0
# mount -o dax /dev/ram0 /mnt/xfs
# echo "test" > /mnt/xfs/testfile
# xfs_io -c "lsattr" /mnt/xfs/testfile
---------------- /mnt/xfs/testfile
# xfs_io -c "chattr +x" /mnt/xfs/testfile
# xfs_io -c "lsattr" /mnt/xfs/testfile
---------------x /mnt/xfs/testfile

I'm wondering if it makes sense to make lsattr print the x flag by
default when XFS is mounted with dax option, that way, we have a method
to know whether dax is used or not on a particular file too.

Thanks,
Eryu

WARNING: multiple messages have this Message-ID (diff)
From: Eryu Guan <eguan@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Jan Kara <jack@suse.cz>,
	linux-nvdimm@lists.01.org,
	"Darrick J.  Wong" <darrick.wong@oracle.com>,
	Dave Chinner <david@fromorbit.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [fstests PATCH v2] xfs: add regression test for DAX mount option usage
Date: Thu, 14 Sep 2017 14:57:41 +0800	[thread overview]
Message-ID: <20170914065741.GH8034@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170911200103.28226-1-ross.zwisler@linux.intel.com>

Hi Ross,

On Mon, Sep 11, 2017 at 02:01:03PM -0600, Ross Zwisler wrote:
> This adds a regression test for the following kernel patch:
> 
>   xfs: always use DAX if mount option is used
> 
> This test will also pass with kernel v4.14-rc1 and beyond because the XFS
> DAX I/O mount option has been disabled (but not removed), so the
> "chattr -x" to turn off DAX doesn't actually do anything.
> 
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> ---
> 
> Changes since v1:
>  - Use perf instead of tracepoints to detect whether DAX is used. (Dan)

Thanks for the test! But I agreed with Dave here, it doesn't seem like a
good idea to depend on the kernel tracepoints in a test, but I can't
think of a better solution either, so I didn't get to this patch
earlier..

Before XFS disabled the ability to switch on & off per-inode DAX flag,
the x flag was only shown after an explicit 'chattr +x', even if XFS was
mounted with dax option, e.g.

# mkfs -t xfs -f /dev/ram0
# mount -o dax /dev/ram0 /mnt/xfs
# echo "test" > /mnt/xfs/testfile
# xfs_io -c "lsattr" /mnt/xfs/testfile
---------------- /mnt/xfs/testfile
# xfs_io -c "chattr +x" /mnt/xfs/testfile
# xfs_io -c "lsattr" /mnt/xfs/testfile
---------------x /mnt/xfs/testfile

I'm wondering if it makes sense to make lsattr print the x flag by
default when XFS is mounted with dax option, that way, we have a method
to know whether dax is used or not on a particular file too.

Thanks,
Eryu
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-09-14  6:57 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 21:08 [PATCH 0/2] xfs: some DAX fixes Ross Zwisler
2017-09-07 21:08 ` Ross Zwisler
2017-09-07 21:08 ` [PATCH 1/2] xfs: always use DAX if mount option is used Ross Zwisler
2017-09-07 21:08   ` Ross Zwisler
2017-09-08  7:20   ` Christoph Hellwig
2017-09-08  7:20     ` Christoph Hellwig
2017-09-08 15:28     ` Ross Zwisler
2017-09-08 15:28       ` Ross Zwisler
2017-09-08 21:21       ` [PATCH] xfs: add regression test for DAX mount option usage Ross Zwisler
2017-09-08 21:21         ` Ross Zwisler
2017-09-11 15:16         ` Ross Zwisler
2017-09-11 15:16           ` Ross Zwisler
2017-09-11 15:37           ` Dan Williams
2017-09-11 15:37             ` Dan Williams
2017-09-11 20:01             ` [fstests PATCH v2] " Ross Zwisler
2017-09-11 20:01               ` Ross Zwisler
2017-09-14  6:57               ` Eryu Guan [this message]
2017-09-14  6:57                 ` Eryu Guan
2017-09-15 22:42                 ` Ross Zwisler
2017-09-15 22:42                   ` Ross Zwisler
2017-09-16 22:26                   ` Dave Chinner
2017-09-16 22:26                     ` Dave Chinner
2017-09-12  6:44         ` [PATCH] " Dave Chinner
2017-09-12  6:44           ` Dave Chinner
2017-09-12 15:38           ` Ross Zwisler
2017-09-12 15:38             ` Ross Zwisler
2017-09-12 23:47             ` Dave Chinner
2017-09-12 23:47               ` Dave Chinner
2017-09-13 14:42               ` Ross Zwisler
2017-09-13 14:42                 ` Ross Zwisler
2017-09-13 22:01                 ` Dave Chinner
2017-09-13 22:01                   ` Dave Chinner
2017-09-13 22:23                   ` Dan Williams
2017-09-13 22:23                     ` Dan Williams
2017-09-13 23:34                     ` Dave Chinner
2017-09-13 23:34                       ` Dave Chinner
2017-09-14  0:28                       ` Dan Williams
2017-09-14  0:28                         ` Dan Williams
2017-09-14  0:40                         ` Dave Chinner
2017-09-14  0:40                           ` Dave Chinner
2017-09-14  1:24                           ` Dan Williams
2017-09-14  1:24                             ` Dan Williams
2017-09-14 12:19                             ` Jeff Moyer
2017-09-14 12:19                               ` Jeff Moyer
2017-09-14 13:16                               ` Johannes Thumshirn
2017-09-14 13:16                                 ` Johannes Thumshirn
2017-09-14 14:10                                 ` Dan Williams
2017-09-14 14:10                                   ` Dan Williams
2017-09-15  9:18                                   ` Johannes Thumshirn
2017-09-15  9:18                                     ` Johannes Thumshirn
2017-09-15 17:39                                     ` Dan Williams
2017-09-15 17:39                                       ` Dan Williams
2017-09-18  7:47                                       ` Johannes Thumshirn
2017-09-18  7:47                                         ` Johannes Thumshirn
2017-09-07 21:08 ` [PATCH 2/2] xfs: validate bdev support for DAX inode flag Ross Zwisler
2017-09-07 21:08   ` Ross Zwisler
2017-09-08  7:21   ` Christoph Hellwig
2017-09-08  7:21     ` Christoph Hellwig

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=20170914065741.GH8034@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-nvdimm@lists.01.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.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.