[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170908153913.jjhzogjs5zpeea5v@thunk.org>
Date: Fri, 8 Sep 2017 11:39:13 -0400
From: Theodore Ts'o <tytso@....edu>
To: Dave Chinner <david@...morbit.com>
Cc: Ross Zwisler <ross.zwisler@...ux.intel.com>,
Andreas Dilger <adilger@...ger.ca>,
Dan Williams <dan.j.williams@...el.com>,
Eric Sandeen <sandeen@...hat.com>,
Lukas Czerner <lczerner@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Christoph Hellwig <hch@....de>, Jan Kara <jack@...e.cz>,
linux-ext4 <linux-ext4@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
xfs <linux-xfs@...r.kernel.org>
Subject: Re: [PATCH 0/9] add ext4 per-inode DAX flag
On Fri, Sep 08, 2017 at 09:25:43AM +1000, Dave Chinner wrote:
> > Okay, so other ideas (which you have also probably already though of) include:
> >
> > 1) Just return -EBUSY if anyone tries to change the DAX flag of an inode with
> > open mappings or any open file handles.
>
> You have to have an open fd to change the flag. :)
What if we only allow the S_DAX flag to be *set*, when i_size and
i_blocks is zero? We could also require that only one file descriptor
be open against the inode, and that it be opened O_RDONLY.
- Ted
Powered by blists - more mailing lists