From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965761AbcAURqY (ORCPT ); Thu, 21 Jan 2016 12:46:24 -0500 Received: from mga04.intel.com ([192.55.52.120]:60010 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965326AbcAURqV (ORCPT ); Thu, 21 Jan 2016 12:46:21 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,326,1449561600"; d="scan'208";a="637950051" 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@ml01.01.org Subject: [PATCH v2 0/5] DAX fsync/msync fixes Date: Thu, 21 Jan 2016 10:45:59 -0700 Message-Id: <1453398364-22537-1-git-send-email-ross.zwisler@linux.intel.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Changes from v1: - Fixed a macro collision for "PMD_INDEX" reported by 0-day for the "tile" architecture: config: tile-allyesconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree make.cross ARCH=tile All warnings (new ones prefixed by >>): >> fs/dax.c:330:0: warning: "PMD_INDEX" redefined [enabled by default] arch/tile/include/asm/pgtable_64.h:35:0: note: this is the location of the previous definition >> fs/dax.c:330:0: warning: "PMD_INDEX" redefined [enabled by default] arch/tile/include/asm/pgtable_64.h:35:0: note: this is the location of the previous definition Thanks, 0-day! 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_v2 --- Original summary: 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. [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