linux-ext4 - [PATCH 0/11 v2] ext4: Convert ext4 DAX IO to iomap framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Tue,  8 Nov 2016 12:08:06 +0100
From:   Jan Kara <jack@...e.cz>
To:     Ted Tso <tytso@....edu>
Cc:     <linux-ext4@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
        Christoph Hellwig <hch@...radead.org>,
        Ross Zwisler <ross.zwisler@...ux.intel.com>,
        Jan Kara <jack@...e.cz>
Subject: [PATCH 0/11 v2] ext4: Convert ext4 DAX IO to iomap framework

Hello,

this is a second revision of my patches to convert ext4 DAX IO paths to the new
iomap framework and removes the old bh-based DAX functions. As a result ext4
gains PMD page fault support, also some other minor bugs get fixed. The patch
set is based on Ross' DAX PMD page fault support series [1]. It passes xfstests
both in DAX and non-DAX mode.

I have pushed out updated version of these patches including the follow-up
DAX patches to:

git://get.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git dax

for easy testing. Once Dave pushes out a stable branch with Ross' patches, we
pull those into ext4 tree and then pull these patches on top of that (provided
nobody will have other objections to the current series).

Changes since v1:
* Changed ext4_iomap_begin() and ext4_iomap_end() to not keep transaction
  handle running between these two functions as that causes lock ordering
  issues.

								Honza

[1] http://www.spinics.net/lists/linux-mm/msg115875.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html