linux-kernel - [PATCH 0/3] Allow fscache to work on BTRFS

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]

Message-ID: <20150420052558.26554.97143.stgit@notabene.brown>
Date:	Mon, 20 Apr 2015 15:27:52 +1000
From:	NeilBrown <neilb@...e.de>
To:	David Howells <dhowells@...hat.com>, Chris Mason <clm@...com>,
	Al Viro <viro@...IV.linux.org.uk>, Josef Bacik <jbacik@...com>,
	David Sterba <dsterba@...e.cz>
Cc:	linux-cachefs@...r.kernel.org, Dave Chinner <david@...morbit.com>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, linux-btrfs@...r.kernel.org
Subject: [PATCH 0/3] Allow fscache to work on BTRFS

The following three patches allow fs to "cachefiles" in a BTRFS
filesystem.

The first is a minor cleanup to cachefiles.
The second is the main change - it teaches cachefile to use
lseek(SEEK_DATA) to find allocated blocks in a file, rather than bmap.
The third patch simply enables this for btrfs.

Thanks,
NeilBrown


---

NeilBrown (3):
      cachefiles: perform test on s_blocksize when opening cache file.
      fscache/cachefiles: optionally use SEEK_DATA instead of ->bmap.
      btrfs: set FS_SUPPORTS_SEEK_HOLE flag.


 fs/btrfs/super.c      |    3 +
 fs/cachefiles/namei.c |   13 ++++-
 fs/cachefiles/rdwr.c  |  125 ++++++++++++++++++++++++++++++-------------------
 include/linux/fs.h    |    1 
 4 files changed, 88 insertions(+), 54 deletions(-)

--
Signature

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/