Re: [PATCH for-6.0 v3 00/20] block/export: Allow exporting BDSs via FUSE

[Kevin Wolf]

Am 27.10.2020 um 20:05 hat Max Reitz geschrieben:
> v1: https://lists.nongnu.org/archive/html/qemu-block/2019-12/msg00451.html
> v2: https://lists.nongnu.org/archive/html/qemu-block/2020-09/msg01611.html
> 
> Branch: https://github.com/XanClic/qemu.git fuse-exports-v3
> Branch: https://git.xanclic.moe/XanClic/qemu.git fuse-exports-v3
> 
> 
> Hi,
> 
> Ever since I found out that you can mount FUSE filesystems on regular
> files (not just directories), I had the idea of adding FUSE block
> exports to qemu where you can export block nodes as raw images.  The
> best thing is that you’d be able to mount an image on itself, so
> whatever format it may be in, qemu lets it appear as a raw image (and
> you can then use regular tools like dd on it).
> 
> The performance is quite bad so far, but we can always try to improve it
> if the need arises.  For now I consider it mostly a cute feature to get
> easy access to the raw contents of image files in any format (without
> requiring root rights).
> 
> 
> This series does the following:
> 
> First, add the FUSE export module (block/export/fuse.c) that implements
> the basic file access functions.  (Note that you need libfuse 3.8.0 or
> later for SEEK_HOLE/SEEK_DATA.)
> 
> Second, it allows using FUSE exports as a protocol in the iotests and
> makes many iotests work with it.  (The file node is exported by a
> background qemu instance to $SOCK_DIR.)
> 
> This gives us a lot of coverage for, well, not free (it does take twelve
> patches), but for cheap; but there are still some more specialized
> things we want to test, so third and last, this series adds an iotest
> dedicated to FUSE exports.

Thanks, applied to the block branch.

Kevin