[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1453347408-22830-1-git-send-email-ross.zwisler@linux.intel.com>
Date: Wed, 20 Jan 2016 20:36:43 -0700
From: Ross Zwisler <ross.zwisler@...ux.intel.com>
To: linux-kernel@...r.kernel.org
Cc: Ross Zwisler <ross.zwisler@...ux.intel.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Dave Chinner <david@...morbit.com>, Jan Kara <jack@...e.com>,
Matthew Wilcox <willy@...ux.intel.com>,
linux-fsdevel@...r.kernel.org, linux-nvdimm@...ts.01.org
Subject: [PATCH 0/5] DAX fsync/msync fixes
This series fixes several issues in v8 of my "DAX fsync/msync support"
patch series [1]. Thank you to Jan Kara for his excellent review.
Jan pointed out that we probably have an issue with the way hole punch
interacts with the fsync/msync code. This is the item that I'll work on
next, but I wanted to send this series out now as I think it will be
independent of the hole punch fixes.
This set applies cleanly on top of v8 of my "DAX fsync/msync support" set,
which is in -mm and -next. That set has not yet been merged for v4.5
which is why the my work tree is still based on -next:
https://git.kernel.org/cgit/linux/kernel/git/zwisler/linux.git/log/?h=fsync_fixes
[1]: https://lists.01.org/pipermail/linux-nvdimm/2016-January/003952.html
Ross Zwisler (5):
dax: never rely on bh.b_dev being set by get_block()
dax: clear TOWRITE flag after flush is complete
dax: improve documentation for fsync/msync
dax: fix PMD handling for fsync/msync
dax: fix clearing of holes in __dax_pmd_fault()
fs/dax.c | 110 +++++++++++++++++++++++++++++++++++++++++++++++++--------------
1 file changed, 86 insertions(+), 24 deletions(-)
--
2.5.0
Powered by blists - more mailing lists