From: "Denis V. Lunev" <den@openvz.org>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: den@openvz.org, Nir Soffer <nirsof@gmail.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
Alberto Garcia <berto@igalia.com>
Subject: [PATCH 1/1] block: improve alignment detection and fix 271 test
Date: Thu, 7 Sep 2023 23:53:26 +0200 [thread overview]
Message-ID: <20230907215326.367847-1-den@openvz.org> (raw)
Unfortunately 271 IO test is broken if started in non-cached mode.
Commits
commit a6b257a08e3d72219f03e461a52152672fec0612
Author: Nir Soffer <nirsof@gmail.com>
Date: Tue Aug 13 21:21:03 2019 +0300
file-posix: Handle undetectable alignment
and
commit 9c60a5d1978e6dcf85c0e01b50e6f7f54ca09104
Author: Kevin Wolf <kwolf@redhat.com>
Date: Thu Jul 16 16:26:00 2020 +0200
block: Require aligned image size to avoid assertion failure
have interesting side effect if used togather.
If the image size is not multiple of 4k and that image falls under
original constraints of Nil's patch, the image can not be opened
due to the check in the bdrv_check_perm().
The patch tries to satisfy the requirements of bdrv_check_perm()
inside raw_probe_alignment(). This is at my opinion better that just
disallowing to run that test in non-cached mode. The operation is legal
by itself.
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Nir Soffer <nirsof@gmail.com>
CC: Kevin Wolf <kwolf@redhat.com>
CC: Hanna Reitz <hreitz@redhat.com>
CC: Alberto Garcia <berto@igalia.com>
---
block/file-posix.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/block/file-posix.c b/block/file-posix.c
index b16e9c21a1..988cfdc76c 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -447,8 +447,21 @@ static void raw_probe_alignment(BlockDriverState *bs, int fd, Error **errp)
for (i = 0; i < ARRAY_SIZE(alignments); i++) {
align = alignments[i];
if (raw_is_io_aligned(fd, buf, align)) {
- /* Fallback to safe value. */
- bs->bl.request_alignment = (align != 1) ? align : max_align;
+ if (align != 1) {
+ bs->bl.request_alignment = align;
+ break;
+ }
+ /*
+ * Fallback to safe value. max_align is perfect, but the size of the device must be multiple of
+ * the virtual length of the device. In the other case we will get a error in
+ * bdrv_node_refresh_perm().
+ */
+ for (align = max_align; align > 1; align /= 2) {
+ if ((bs->total_sectors * BDRV_SECTOR_SIZE) % align == 0) {
+ break;
+ }
+ }
+ bs->bl.request_alignment = align;
break;
}
}
--
2.34.1
next reply other threads:[~2023-09-07 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 21:53 Denis V. Lunev [this message]
2023-09-19 11:53 ` [PATCH 1/1] block: improve alignment detection and fix 271 test Denis V. Lunev
2023-09-26 20:02 ` Denis V. Lunev
2023-10-02 7:29 ` Denis V. Lunev
2023-10-13 9:54 ` Denis V. Lunev
2023-10-14 11:23 ` Nir Soffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230907215326.367847-1-den@openvz.org \
--to=den@openvz.org \
--cc=berto@igalia.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=nirsof@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).