Re: switch loop and target to use ITER_BVEC iov_iter V2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jan 25, 2015 at 09:11:57PM +0100, Christoph Hellwig wrote:
> This series adds two new helpers to easily read from and write to
> arbitrary iov_iter structures and switches the loop driver and target file
> backend to use those with bio_vecs.
> 
> Using bio_vecs directly avoids the need to kmap individual elements in
> the callers, which is epecially important in the target driver, and also
> gets rid of the horrible splice code abuse hack in the loop driver.
> 
> Changes since V1:
> 	- rebase ontop of viro/for-next
> 	- changed the helpers to read/write any iov_iter, and use
> 	  iov_iter_bvec to build those
> 	- return -EINVAL if ->read_iter/->write_iter aren't present
> 	  instead of -EBADFD
> 	- use kcalloc in the target patch
> 	- add a patch to rewrite the target WRITE SAME emulation

Applied, with iov_iter_bvec() direction argument matching the actual
direction of copying intended.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux