From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v2 6/6] tests/9p: Test `Tsetattr` can truncate unlinked file
Date: Wed, 12 Mar 2025 15:34:44 +0100 [thread overview]
Message-ID: <1900886.tBiGGRzFWv@silver> (raw)
In-Reply-To: <20250312152520.25f3dd79@bahia>
On Wednesday, March 12, 2025 3:25:20 PM CET Greg Kurz wrote:
> On Wed, 12 Mar 2025 15:11:41 +0100
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
>
> > On Tuesday, March 11, 2025 6:28:09 PM CET Greg Kurz wrote:
> > > Enhance the `use-after-unlink` test with a new check for the
> > > case where the client wants to alter the size of an unlinked
> > > file for which it still has an active fid.
> > >
> > > Suggested-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> > > Signed-off-by: Greg Kurz <groug@kaod.org>
> > > ---
> > > tests/qtest/virtio-9p-test.c | 8 ++++++++
> > > 1 file changed, 8 insertions(+)
> > >
> > > diff --git a/tests/qtest/virtio-9p-test.c b/tests/qtest/virtio-9p-test.c
> > > index f515a9bb157b..20c0d744fa56 100644
> > > --- a/tests/qtest/virtio-9p-test.c
> > > +++ b/tests/qtest/virtio-9p-test.c
> > > @@ -736,6 +736,14 @@ static void fs_use_after_unlink(void *obj, void *data,
> > > .data = buf
> > > }).count;
> > > g_assert_cmpint(count, ==, write_count);
> > > +
> > > + /* truncate file to (arbitrarily chosen) size 2001 */
> > > + tsetattr({
> > > + .client = v9p, .fid = fid_file, .attr = (v9fs_attr) {
> > > + .valid = P9_SETATTR_SIZE,
> > > + .size = 2001
> > > + }
> > > + });
> > > }
> > >
> > > static void cleanup_9p_local_driver(void *data)
> > >
> >
> > Ah, I just meant the code snippet as a starting point, like I would have also
> > checked with a stat() call whether 9p server really did what it promised.
> >
> > But OK, better some test coverage than nothing. :)
> >
>
> FWIW the server returns ENOENT if it doesn't have the fix which causes
> the check to fail. I was assuming this would be enough but I'm fine with
> adding an extra check if you want.
Yeah, that's why I wasn't really anxious about it. If you have some cycles,
fine, I'll guess you can just copy & paste existing stat() code from another
test, otherwise deferred into future, NP.
Thanks!
/Christian
prev parent reply other threads:[~2025-03-12 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 17:28 [PATCH v2 0/6] 9pfs: Fix ftruncate-after-unlink Greg Kurz
2025-03-11 17:28 ` [PATCH v2 1/6] 9pfs: local : Introduce local_fid_fd() helper Greg Kurz
2025-03-12 14:00 ` Christian Schoenebeck
2025-03-11 17:28 ` [PATCH v2 2/6] 9pfs: Don't use file descriptors in core code Greg Kurz
2025-03-12 14:02 ` Christian Schoenebeck
2025-03-11 17:28 ` [PATCH v2 3/6] 9pfs: Introduce ftruncate file op Greg Kurz
2025-03-12 14:07 ` Christian Schoenebeck
2025-03-12 14:21 ` Greg Kurz
2025-03-11 17:28 ` [PATCH v2 4/6] 9pfs: Introduce futimens " Greg Kurz
2025-03-11 17:28 ` [PATCH v2 5/6] tests/9p: add 'Tsetattr' request to test client Greg Kurz
2025-03-11 17:28 ` [PATCH v2 6/6] tests/9p: Test `Tsetattr` can truncate unlinked file Greg Kurz
2025-03-12 14:11 ` Christian Schoenebeck
2025-03-12 14:25 ` Greg Kurz
2025-03-12 14:34 ` Christian Schoenebeck [this message]
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=1900886.tBiGGRzFWv@silver \
--to=qemu_oss@crudebyte.com \
--cc=farosas@suse.de \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.