From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com ([134.134.136.24]:36772 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752159AbcAUDhD (ORCPT ); Wed, 20 Jan 2016 22:37:03 -0500 From: Ross Zwisler To: linux-kernel@vger.kernel.org Cc: Ross Zwisler , Alexander Viro , Andrew Morton , Dan Williams , Dave Chinner , Jan Kara , Matthew Wilcox , linux-fsdevel@vger.kernel.org, linux-nvdimm@lists.01.org Subject: [PATCH 0/5] DAX fsync/msync fixes Date: Wed, 20 Jan 2016 20:36:43 -0700 Message-Id: <1453347408-22830-1-git-send-email-ross.zwisler@linux.intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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