From: Hanna Czenczek <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Hanna Czenczek <hreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Sam Li <faithilikerun@gmail.com>
Subject: [PATCH 0/5] file-posix: Clean up and fix zoned checks
Date: Thu, 24 Aug 2023 17:53:39 +0200 [thread overview]
Message-ID: <20230824155345.109765-1-hreitz@redhat.com> (raw)
Hi,
As presented in [1] there is a bug in the zone code in raw_co_prw(),
specifically we don’t check whether there actually is zone information
before running code that assumes there is (and thus we run into a
division by zero). This has now also been reported in [2].
I believe the solution [1] is incomplete, though, which is why I’m
sending this separate series: I don’t think checking bs->wps and/or
bs->bl.zone_size to determine whether there is zone information is
right; for example, we do not have raw_refresh_zoned_limits() clear
those values if on a refresh, zone information were to disappear.
It is also weird that we separate checking bs->wps and bs->bl.zone_size
at all; raw_refresh_zoned_limits() seems to intend to ensure that either
we have information with non-NULL bs->wps and non-zero bs->bl.zone_size,
or we don’t.
I think we should have a single flag that tells whether we have valid
information or not, and it looks to me like bs->bl.zoned != BLK_Z_NONE
is the condition that fits best.
Patch 1 ensures that raw_refresh_zoned_limits() will set bs->bl.zoned to
BLK_Z_NONE on error, so that we can actually be sure that this condition
tells us whether we have valid information or not.
Patch 2 unifies all conditional checks for zone information to use
bs->bl.zoned != BLK_Z_NONE.
Patch 3 is the I/O error path fix, which is not really different from
[1].
Patch 4 does a bit of clean-up.
Patch 5 adds a regression test.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2023-06/msg01742.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2234374
Hanna Czenczek (5):
file-posix: Clear bs->bl.zoned on error
file-posix: Check bs->bl.zoned for zone info
file-posix: Fix zone update in I/O error path
file-posix: Simplify raw_co_prw's 'out' zone code
tests/file-io-error: New test
block/file-posix.c | 42 +++++----
tests/qemu-iotests/tests/file-io-error | 99 ++++++++++++++++++++++
tests/qemu-iotests/tests/file-io-error.out | 31 +++++++
3 files changed, 150 insertions(+), 22 deletions(-)
create mode 100755 tests/qemu-iotests/tests/file-io-error
create mode 100644 tests/qemu-iotests/tests/file-io-error.out
--
2.41.0
next reply other threads:[~2023-08-24 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 15:53 Hanna Czenczek [this message]
2023-08-24 15:53 ` [PATCH 1/5] file-posix: Clear bs->bl.zoned on error Hanna Czenczek
2023-08-24 16:57 ` Sam Li
2023-08-24 15:53 ` [PATCH 2/5] file-posix: Check bs->bl.zoned for zone info Hanna Czenczek
2023-08-24 16:58 ` Sam Li
2023-08-24 15:53 ` [PATCH 3/5] file-posix: Fix zone update in I/O error path Hanna Czenczek
2023-08-24 17:17 ` Sam Li
2023-08-24 15:53 ` [PATCH 4/5] file-posix: Simplify raw_co_prw's 'out' zone code Hanna Czenczek
2023-08-24 17:18 ` Sam Li
2023-08-24 15:53 ` [PATCH 5/5] tests/file-io-error: New test Hanna Czenczek
2023-08-24 16:53 ` [PATCH 0/5] file-posix: Clean up and fix zoned checks Sam Li
2023-09-21 18:21 ` Michael Tokarev
2023-09-21 18:52 ` Michael Tokarev
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=20230824155345.109765-1-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=faithilikerun@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).