public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 4/4] xfs: XFS_DIFLAG2_DAX limited by PAGE_SIZE
Date: Mon, 15 Feb 2016 18:12:04 -0600	[thread overview]
Message-ID: <56C26954.2010001@sandeen.net> (raw)
In-Reply-To: <1455513734-15192-5-git-send-email-david@fromorbit.com>



On 2/14/16 11:22 PM, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
> 
> If the block size of a filesystem is not at least PAGE_SIZEd, then
> at this point in time DAX cannot be used due to the fact we can't
> guarantee extents are page sized or aligned without further work.
> Hence disallow setting the DAX flag on an inode if the block size is
> too small. Also, be defensive and check the block size when reading
> an inode in off disk.
> 
> In future, we want to allow DAX to work on any filesystem, so this
> is temporary while we sort of the correct conbination of extent size
> hints and allocation alignment configurations needed to guarantee
> page sized and aligned extent allocation for DAX enabled files.
> 
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
>  fs/xfs/xfs_ioctl.c | 12 ++++++++----
>  fs/xfs/xfs_iops.c  |  1 +
>  2 files changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index a870d16..8e9cd3c 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -1080,11 +1080,15 @@ xfs_ioctl_setattr_dax_invalidate(
>  
>  	/*
>  	 * It is only valid to set the DAX flag on regular files and
> -	 * directories. On directories it serves as an inherit hint.
> +	 * directories on filesystems where the block size is at least the page
                                                              ^^^^^^^^
> +	 * size. On directories it serves as an inherit hint.
>  	 */
> -	if ((fa->fsx_xflags & FS_XFLAG_DAX) &&
> -	    !(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode)))
> -		return -EINVAL;
> +	if (fa->fsx_xflags & FS_XFLAG_DAX) {
> +		if (!(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode)))
> +			return -EINVAL;
> +		if (ip->i_mount->m_sb.sb_blocksize != PAGE_SIZE)
                                                   ^^

So which is it, at least PAGE_SIZE or == PAGE_SIZE?

> +			return -EINVAL;
> +	}
>  
>  	/* If the DAX state is not changing, we have nothing to do here. */
>  	if ((fa->fsx_xflags & FS_XFLAG_DAX) && IS_DAX(inode))
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index 9c984a0..fb7dc61 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -1186,6 +1186,7 @@ xfs_diflags_to_iflags(
>  	if (flags & XFS_DIFLAG_NOATIME)
>  		inode->i_flags |= S_NOATIME;
>  	if (S_ISREG(inode->i_mode) &&
> +	    ip->i_mount->m_sb.sb_blocksize == PAGE_SIZE &&
>  	    (ip->i_mount->m_flags & XFS_MOUNT_DAX ||
>  	     ip->i_d.di_flags2 & XFS_DIFLAG2_DAX))
>  		inode->i_flags |= S_DAX;

Is it possible to get mounted with XFS_MOUNT_DAX if blocksize != PAGE_SIZE?
If so, should it be?  This seems like a strange place to catch this mismatch.

-Eric

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

  reply	other threads:[~2016-02-16  0:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  5:22 [PATCH 0/4] xfs: fixes for XFS_DIFLAG2_DAX support Dave Chinner
2016-02-15  5:22 ` [PATCH 1/4] xfs: XFS_DIFLAG_DAX is only for regular files or directories Dave Chinner
2016-02-15  5:22 ` [PATCH 2/4] xfs: S_DAX is only for regular files Dave Chinner
2016-02-15  5:22 ` [PATCH 3/4] xfs: dynamically switch modes when XFS_DIFLAG2_DAX is set/cleared Dave Chinner
2016-02-17  7:31   ` [PATCH 3/4 v2] " Dave Chinner
2016-02-17 20:57     ` Ross Zwisler
2016-02-15  5:22 ` [PATCH 4/4] xfs: XFS_DIFLAG2_DAX limited by PAGE_SIZE Dave Chinner
2016-02-16  0:12   ` Eric Sandeen [this message]
2016-02-16  0:39     ` Dave Chinner
2016-02-16  0:54       ` Eric Sandeen
2016-02-16 23:53 ` [PATCH 0/4] xfs: fixes for XFS_DIFLAG2_DAX support Ross Zwisler
2016-02-17  0:23   ` Dave Chinner
2016-02-17 20:04 ` Brian Foster
2016-02-17 22:56 ` 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=56C26954.2010001@sandeen.net \
    --to=sandeen@sandeen.net \
    --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