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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 29 Nov 2021 11:21:34 +0100 From: Christoph Hellwig <hch@....de> To: Dan Williams <dan.j.williams@...el.com> Cc: Mike Snitzer <snitzer@...hat.com>, Ira Weiny <ira.weiny@...el.com>, dm-devel@...hat.com, linux-xfs@...r.kernel.org, nvdimm@...ts.linux.dev, linux-s390@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-erofs@...ts.ozlabs.org, linux-ext4@...r.kernel.org, virtualization@...ts.linux-foundation.org Subject: decouple DAX from block devices v2 Hi Dan, this series decouples the DAX from the block layer so that the block_device is not needed at all for the DAX I/O path. Changes since v1: - rebase on latest v5.16-rc - ensure the new dax zeroing helpers are always declared - fix a dax_dev leak in pmem_attach_disk - remove '\n' from an xfs format string - fix a pre-existing error handling bug in alloc_dev - fix a few whitespace issues - tighten an error check - use s64/u64 a little more - improve a few commit messages - add a CONFIG_FS_DAX ifdef to stub out IOMAP_DAX - improve how IOMAP_DAX is introduced and better document why it is added
Powered by blists - more mailing lists