On Fri, Oct 2, 2015 at 2:02 PM, Ross Zwisler <[email protected]> wrote: > This reverts commit 8346c416d17bf5b4ea1508662959bb62e73fd6a5. > > This commit did fix the issue it intended to fix, but it turns out that > the locking changes 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") > > had other issues as well, so they need to just be reverted.
Wait, why introduce two points in the kernel history where we have a known uninitialized variable? I'd say fix up the revert of "mm: take i_mmap_lock in unmap_mapping_range() for DAX" to address the conflict with the fix, one less patch and keeps the stability rolling forward. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
