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
| ||
|
Date: Thu, 24 Aug 2017 17:35:43 -0700 From: Dan Williams <dan.j.williams@...el.com> To: linux-fsdevel@...r.kernel.org Cc: jack@...e.cz, "Darrick J. Wong" <darrick.wong@...cle.com>, linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org, Andreas Dilger <adilger.kernel@...ger.ca>, Jan Kara <jack@...e.com>, Theodore Ts'o <tytso@....edu>, hch@....de Subject: [PATCH 0/2] fs: cache dax_device lookup result Christoph notes: I just noticed that we now do a fs_dax_get_by_host in every iomap_begin call for DAX. This function iterates a list, does a string compared and igrab. I really think we need to cache this in the superblock (possible even the fs superblock) similar to what we do for the block device. Fix this up to cache the result of the dax_device lookup in 'struct xfs_mount' for xfs and 'struct super_block' for ext2/ext4. --- Dan Williams (2): xfs: cache dax_device lookup result ext2, ext4: cache dax_device lookup result fs/ext2/inode.c | 11 +++++++---- fs/ext4/inode.c | 11 +++++++---- fs/xfs/xfs_aops.c | 24 ++++++++++++++++++++++++ fs/xfs/xfs_aops.h | 1 + fs/xfs/xfs_buf.h | 1 + fs/xfs/xfs_iomap.c | 9 +-------- include/linux/fs.h | 3 +++ 7 files changed, 44 insertions(+), 16 deletions(-)
Powered by blists - more mailing lists