Using uuid as a bitmap name is too restrictive. We are going to
expose bitmap names to libvirt where we cannot expect users to
follow such constraint.
QEMU allows bitmap names up to 1024 symbols, but this seems too
big for the structure. We do not want to mess with dynamic length,
so set the max le
Currently blk-cbt use UUID as a name. This is a big limitation.
We are going to expose bitmap names to libvirt, so we should
not expect users to follow this. Moreover, even VHI backup
utilities use non-UUID names sometimes. Technically QEMU
allows us bitmap names up to 1024 bytes, but 128 should be
Store cbts in a list instead of a single pointer. Allow
up to 16 entries.
Update all APIs to work with user-specified bitmap.
We need to exercise extra care when accessing queue->cbt_list
to be sure that accessed element still exists. Majority of
accesses, which are mostly user-space ioctls, are p
so user can query the list of active bitmaps.
https://virtuozzo.atlassian.net/browse/VSTOR-96269
Signed-off-by: Andrey Zhadchenko
---
v2:
- add abi version
- remove total_count from struct blk_user_cbt_list
block/blk-cbt.c | 36
block/ioctl.c
Users could rename cbts with CI_FLAG_NEW_NAME flag during
BLKCBTSET ioctl. Set command now uses ci_name to identify
target, so we need a new field to present updated name.
Add new BLKCBTRENAME ioctl instead of adding new fields to
blk_user_cbt_info.
Note that we do not need to extra protect cbt->n
so it will be easier to change anything in the future
https://virtuozzo.atlassian.net/browse/VSTOR-96269
Signed-off-by: Andrey Zhadchenko
---
block/blk-cbt.c | 10 ++
include/uapi/linux/fs.h | 4
2 files changed, 14 insertions(+)
diff --git a/block/blk-cbt.c b/block/blk-cb
https://virtuozzo.atlassian.net/browse/VSTOR-98105
Signed-off-by: Pavel Tikhomirov
Pavel Tikhomirov (2):
vhost/vsock: split out vhost_vsock_drop_backends helper
vhost/vsock: add VHOST_RESET_OWNER ioctl
drivers/vhost/vsock.c | 56 ---
1 file changed, 4
We plan to use it to be able to execute new qemu version and take over
the contol over /dev/vhost-vsock file by reseting the owner and setting
a new one. We expect not to lose any AF_VSOCK connection while this
happens.
https://virtuozzo.atlassian.net/browse/VSTOR-98105
Signed-off-by: Pavel Tikhom
Reviewed-by: Pavel Tikhomirov
On 1/28/25 16:15, Andrey Zhadchenko wrote:
Currently blk-cbt use UUID as a name. This is a big limitation.
We are going to expose bitmap names to libvirt, so we should
not expect users to follow this. Moreover, even VHI backup
utilities use non-UUID names sometimes
Split the actual backend dropping part from vhost_vsock_stop, we will
need to use it where vsock->dev.mutex is already taken and owner is
checked.
https://virtuozzo.atlassian.net/browse/VSTOR-98105
Signed-off-by: Pavel Tikhomirov
---
drivers/vhost/vsock.c | 26 +-
1 file
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.7
-->
commit 5eb9590b303d5f92a72ecb39d7cc3c0ed1b27b01
Author: Andrey Zhadchenko
Date: Tue Jan 28 11:15:05 2025 +0300
block/blk-cb
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.7
-->
commit 0d3dc1c86af908554c169a1b03b1a585279a48f0
Author: Andrey Zhadchenko
Date: Tue Jan 28 11:15:06 2025 +0300
block/blk-cb
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.7
-->
commit 3684562b9ec0e5fe8d9362ff0d006da3a86aecf0
Author: Andrey Zhadchenko
Date: Tue Jan 28 11:15:08 2025 +0300
block/blk-cb
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.7
-->
commit a9f7d2a1874eca7f2a4f1f3ade3ee8a23e750c0e
Author: Andrey Zhadchenko
Date: Tue Jan 28 11:15:09 2025 +0300
block/blk-cb
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.7
-->
commit c692713fc23739893b1bfa0fc6a7da514fd7b3a5
Author: Andrey Zhadchenko
Date: Tue Jan 28 11:15:07 2025 +0300
block/blk-cb
The commit is pushed to "branch-rh7-3.10.0-1160.119.1.vz7.224.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh7-3.10.0-1160.119.1.vz7.224.5
-->
commit 2ebd55d0b735906ca6088e5c0ebbdbd3a68da2d7
Author: Pavel Tikhomirov
Date: Mon Jan 27 15:15:00 2025 +0800
ve: rew
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.8
-->
commit 31d603dfc116ddaadf4167eb823a333ba805163f
Author: Pavel Tikhomirov
Date: Tue Jan 28 18:48:00 2025 +0800
vhost/vsock:
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.8
-->
commit ad35221ad13416f3eb981d5f2c33312dd88fa692
Author: Pavel Tikhomirov
Date: Tue Jan 28 18:48:01 2025 +0800
vhost/vsock:
The commit is pushed to "branch-rh9-5.14.0-427.44.1.vz9.80.x-ovz" and will
appear at g...@bitbucket.org:openvz/vzkernel.git
after rh9-5.14.0-427.44.1.vz9.80.8
-->
commit 78870d51913bd072aa62f0b5a0b0b9d92655f3c2
Author: Liu Kui
Date: Tue Jan 28 13:43:52 2025 +0800
fs/fuse kio: get the c
19 matches
Mail list logo