From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: disable per-inode DAX flag
Date: Wed, 30 Aug 2017 09:17:01 -0700 [thread overview]
Message-ID: <20170830161701.GM4757@magnolia> (raw)
In-Reply-To: <20170830145119.3013-1-hch@lst.de>
On Wed, Aug 30, 2017 at 04:51:19PM +0200, Christoph Hellwig wrote:
> Currently flag switching can be used to easily crash the kernel. Disable
> the per-inode DAX flag until that is sorted out.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/xfs_ioctl.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index 9c0c7a920304..06ca244c323a 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -1008,11 +1008,12 @@ xfs_diflags_to_linux(
> inode->i_flags |= S_NOATIME;
> else
> inode->i_flags &= ~S_NOATIME;
> +#if 0 /* disabled until the flag switching races are sorted out */
#ifdef DEBUG ?
So that we developers can play with DAX without having to patch this out?
If that's fine with you I'll just change it on the way in.
--D
> if (xflags & FS_XFLAG_DAX)
> inode->i_flags |= S_DAX;
> else
> inode->i_flags &= ~S_DAX;
> -
> +#endif
> }
>
> static int
> --
> 2.11.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-08-30 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 14:51 [PATCH] xfs: disable per-inode DAX flag Christoph Hellwig
2017-08-30 16:17 ` Darrick J. Wong [this message]
2017-08-30 16:17 ` Christoph Hellwig
2017-08-30 16:56 ` 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=20170830161701.GM4757@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
/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