On Wed, Apr 08, 2020 at 03:07:35PM -0700, Ira Weiny wrote:
> On Thu, Apr 09, 2020 at 07:02:36AM +1000, Dave Chinner wrote:
> > On Wed, Apr 08, 2020 at 10:09:23AM -0700, Ira Weiny wrote:
>
> [snip]
>
> > >
> > > This sounds good but I think we need a slight modification to make the function equivalent in functionality.
> > >
> > > void
> > > xfs_diflags_to_iflags(
> > > struct xfs_inode *ip,
> > > bool init)
> > > {
> > > struct inode *inode = VFS_I(ip);
> > > unsigned int xflags = xfs_ip2xflags(ip);
> > > unsigned int flags = 0;
> > >
> > > inode->i_flags &= ~(S_IMMUTABLE | S_APPEND | S_SYNC | S_NOATIME |
> > > S_DAX);
> >
> > We don't want to clear the dax flag here, ever, if it is already
> > set. That is an externally visible change and opens us up (again) to
> > races where IS_DAX() changes half way through a fault path. IOWs, avoiding
> > clearing the DAX flag was something I did explicitly in the above
> > code fragment.
>
> <sigh> yes... you are correct.
>
> But I don't like depending on the caller to clear the S_DAX flag if
> xfs_inode_enable_dax() is false. IMO this function should clear the flag in
> that case for consistency...
No. We simply cannot do that here except in the init case when the
inode is not yet visible to userspace. In which case, we know -for
certain- that the S_DAX is not set, and hence we do not need to
clear it. Initial conditions matter!
If you want to make sure of this, add this:
ASSERT(!(IS_DAX(inode) && init));
And now we'll catch inodes that incorrectly have S_DAX set at init
time.
> > memory S_DAX flag, we can actually clear the on-disk flag
> > safely, so that next time the inode cycles into memory it won't
> > be using DAX. IOWs, admins can stop the applications, clear the
> > DAX flag and drop caches. This should result in the inode being
> > recycled and when the app is restarted it will run without DAX.
> > No ned for deleting files, copying large data sets, etc just to
> > turn off an inode flag.
>
> We already discussed evicting the inode and it was determined to
> be too confusing.[*]
That discussion did not even consider how admins are supposed to
clear the inode flag once it is set on disk. It was entirely
focussed around "we can't change in memory S_DAX state" and how the
tri-state mount option to "override" the on-disk flag could be done.
Nobody noticed that being unable to rmeove the on-disk flag means
the admin's only option to turn off dax for an application is to
turn it off for everything, filesystem wide, which requires:
1. stopping the app.
2. stopping every other app using the filesystem
3. unmounting the filesystem
4. changing to dax=never mount option
5. mounting the filesystem
6. restarting all apps.
It's a hard stop for everything using the filesystem, and it changes
the runtime environment for all applications, not just the one that
needs DAX turned off. Not to mention that if it's the root
filesystem that is using DAX, then it's a full system reboot needed
to change the mount options.
IMO, this is a non-starter from a production point of view - testing
and qualification of all applications rather than just the affected
app is required to make this sort of change. It simply does not
follow the "minimal change to fix the problem" rules for managing
issues in production environments.
So, pLease explain to me how this process:
1. stop the app
2. remove inode flags via xfs_io
3. run drop_caches
4. start the app
is worse than requiring admins to unmount the filesystem to turn off
DAX for an application.
> Furthermore, if we did want an interface like that why not allow
> the on-disk flag to be set as well as cleared?
Well, why not - it's why I implemented the flag in the first place!
The only problem we have here is how to safely change the in-memory
DAX state, and that largely has nothing to do with setting/clearing
the on-disk flag....
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
