| From: |
| Johannes Thumshirn <Johannes.Thumshirn-AT-wdc.com> |
| To: |
| "linux-block-AT-vger.kernel.org" <linux-block-AT-vger.kernel.org> |
| Subject: |
| [ANNOUNCE] zloopctl - a small zloop administration utility |
| Date: |
| Fri, 17 Oct 2025 08:00:01 +0000 |
| Message-ID: |
| <8c78d32e-ff56-4fc3-8624-3e2a6cff2439@wdc.com> |
| Cc: |
| "linux-btrfs-AT-vger.kernel.org" <linux-btrfs-AT-vger.kernel.org>, "linux-xfs-AT-vger.kernel.org" <linux-xfs-AT-vger.kernel.org>, "linux-fsdevel-AT-vger.kernel.org" <linux-fsdevel-AT-vger.kernel.org> |
| Archive-link: |
| Article |
Hi all,
I've hacked together a small utility on the spirit of losetup(8) for
administering zloop devices. I've done this because I felt there's a
need for something a bit more user friendly than 'echo $ALL_MY_ARGS >>
/dev/zloop-control'. That of course means you can still use echo in
projects like blktests of fstests, to not create any dependencies on
foreign projects.
The project was started to lower the entry barrier into using zloop
devices for testing filesystems and/or user-space tools operating on
zoned block devices.
Please find the source here:
https://github.com/morbidrsa/zloopctl
Pull-request (or patches) welcome.
And yes this is written in Rust and could've been bash, I know.
Byte,
Johannes
