From: Amjad Alsharafi <amjadsharafi10@gmail.com>
To: qemu-devel@nongnu.org
Cc: Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
"open list:vvfat" <qemu-block@nongnu.org>,
Amjad Alsharafi <amjadsharafi10@gmail.com>
Subject: [PATCH v2 0/5] vvfat: Fix write bugs for large files and add iotests
Date: Sat, 4 May 2024 16:44:18 +0800 [thread overview]
Message-ID: <cover.1714811679.git.amjadsharafi10@gmail.com> (raw)
v2:
Added iotests for `vvfat` driver along with a simple `fat16` module to run the tests.
v1:
https://patchew.org/QEMU/20240327201231.31046-1-amjadsharafi10@gmail.com/
Fix the issue of writing to the middle of the file in vvfat
Amjad Alsharafi (5):
vvfat: Fix bug in writing to middle of file
vvfat: Fix usage of `info.file.offset`
vvfat: Fix reading files with non-continuous clusters
iotests: Add `vvfat` tests
iotests: Filter out `vvfat` fmt from failing tests
.gitlab-ci.d/buildtest.yml | 1 +
block/vvfat.c | 32 +-
tests/qemu-iotests/001 | 1 +
tests/qemu-iotests/002 | 1 +
tests/qemu-iotests/003 | 1 +
tests/qemu-iotests/005 | 1 +
tests/qemu-iotests/008 | 1 +
tests/qemu-iotests/009 | 1 +
tests/qemu-iotests/010 | 1 +
tests/qemu-iotests/011 | 1 +
tests/qemu-iotests/012 | 1 +
tests/qemu-iotests/021 | 1 +
tests/qemu-iotests/032 | 1 +
tests/qemu-iotests/033 | 1 +
tests/qemu-iotests/052 | 1 +
tests/qemu-iotests/094 | 1 +
tests/qemu-iotests/120 | 2 +-
tests/qemu-iotests/140 | 1 +
tests/qemu-iotests/145 | 1 +
tests/qemu-iotests/157 | 1 +
tests/qemu-iotests/159 | 2 +-
tests/qemu-iotests/170 | 2 +-
tests/qemu-iotests/192 | 1 +
tests/qemu-iotests/197 | 2 +-
tests/qemu-iotests/208 | 2 +-
tests/qemu-iotests/215 | 2 +-
tests/qemu-iotests/236 | 2 +-
tests/qemu-iotests/251 | 1 +
tests/qemu-iotests/307 | 2 +-
tests/qemu-iotests/308 | 2 +-
tests/qemu-iotests/check | 2 +-
tests/qemu-iotests/fat16.py | 507 ++++++++++++++++++
tests/qemu-iotests/meson.build | 3 +-
.../tests/export-incoming-iothread | 2 +-
tests/qemu-iotests/tests/fuse-allow-other | 1 +
.../tests/mirror-ready-cancel-error | 2 +-
tests/qemu-iotests/tests/regression-vhdx-log | 1 +
tests/qemu-iotests/tests/vvfat | 400 ++++++++++++++
tests/qemu-iotests/tests/vvfat.out | 5 +
39 files changed, 967 insertions(+), 26 deletions(-)
create mode 100644 tests/qemu-iotests/fat16.py
create mode 100755 tests/qemu-iotests/tests/vvfat
create mode 100755 tests/qemu-iotests/tests/vvfat.out
--
2.44.0
next reply other threads:[~2024-05-04 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 8:44 Amjad Alsharafi [this message]
2024-05-04 8:44 ` [PATCH v2 1/5] vvfat: Fix bug in writing to middle of file Amjad Alsharafi
2024-05-04 8:44 ` [PATCH v2 2/5] vvfat: Fix usage of `info.file.offset` Amjad Alsharafi
2024-05-04 8:44 ` [PATCH v2 3/5] vvfat: Fix reading files with non-continuous clusters Amjad Alsharafi
2024-05-04 8:44 ` [PATCH v2 4/5] iotests: Add `vvfat` tests Amjad Alsharafi
2024-05-04 8:44 ` [PATCH v2 5/5] iotests: Filter out `vvfat` fmt from failing tests Amjad Alsharafi
2024-05-04 8:51 ` [PATCH v2 0/5] vvfat: Fix write bugs for large files and add iotests Amjad Alsharafi
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=cover.1714811679.git.amjadsharafi10@gmail.com \
--to=amjadsharafi10@gmail.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).