[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1444170529-12814-1-git-send-email-ross.zwisler@linux.intel.com>
Date: Tue, 6 Oct 2015 16:28:47 -0600
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>,
Matthew Wilcox <willy@...ux.intel.com>,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Dave Chinner <david@...morbit.com>, Jan Kara <jack@...e.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
linux-nvdimm@...ts.01.org,
Matthew Wilcox <matthew.r.wilcox@...el.com>
Subject: [PATCH v4 0/2] Revert locking changes in DAX for v4.3
This series reverts some recent changes to the locking scheme in DAX introduced
by these two commits:
commit 843172978bb9 ("dax: fix race between simultaneous faults")
commit 46c043ede471 ("mm: take i_mmap_lock in unmap_mapping_range() for DAX")
Changes from v3:
- reduced the revert of 46c043ede471 in patch 1 so that we still drop the
mapping->i_mmap_rwsem before calling unmap_mapping_range(). This prevents
the deadlock in the __dax_pmd_fault() path so there is no longer a need to
temporarily disable DAX PMD faults.
Ross Zwisler (2):
Revert "mm: take i_mmap_lock in unmap_mapping_range() for DAX"
Revert "dax: fix race between simultaneous faults"
fs/dax.c | 70 +++++++++++++++++++++++++------------------------------------
mm/memory.c | 2 ++
2 files changed, 31 insertions(+), 41 deletions(-)
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists