[PATCH v3 0/3] Revert locking changes in DAX for v4.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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")

It also temporarily disables the newly added DAX PMD fault path because of a
deadlock. We are re-working the way that DAX does its locking for v4.4, so for
now just disable DAX PMD faults and fall back to PAGE_SIZE faults to make sure
we don't hit this deadlock.

Changes from v2:
 - Temporarily disable the DAX PMD fault path while we re-work DAX locking for
   v4.4.

Ross Zwisler (3):
  Revert "mm: take i_mmap_lock in unmap_mapping_range() for DAX"
  Revert "dax: fix race between simultaneous faults"
  dax: temporarily disable DAX PMD fault path

 fs/dax.c    | 90 ++++++++++++++++++++++++++++---------------------------------
 mm/memory.c |  2 ++
 2 files changed, 43 insertions(+), 49 deletions(-)

-- 
2.1.0

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]