From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH 1/6] tests/9p: add 'use-after-unlink' test
Date: Mon, 25 Nov 2024 10:34:57 +0100 [thread overview]
Message-ID: <1935071.n0I2rtNXNV@silver> (raw)
In-Reply-To: <20241125094717.50e0344b@bahia>
On Monday, November 25, 2024 9:47:17 AM CET Greg Kurz wrote:
> Hi Christian,
>
> On Wed, 21 Feb 2024 15:13:13 +0100
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
>
> > After removing a file from the file system, we should still be able to
> > work with the file if we already had it open before removal.
> >
> > As a first step we verify that it is possible to write to an unlinked
> > file, as this is what already works. This test is extended later on
> > after having fixed other use cases after unlink that are not working
> > yet.
> >
> > Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> > ---
>
> Test looks good but make sure it is merged last to preserve bisect.
I think there is a misapprehension: this test already passed! So no need to
move this patch.
What this test does is verifying the scenario open-unlink-write. I already
sent this patch in February and was surprised by myself that this idiom
already works:
https://lore.kernel.org/all/E1rcnYJ-0004KK-LV@lizzy.crudebyte.com/
What this entire series (i.e. patch 5) rather fixes is the idiom
open-unlink-fstat, and the test for this idiom is the last patch, not this
first one here.
So bisect is already fine.
> Reviewed-by: Greg Kurz <groug@kaod.org>
Thanks!
/Christian
next prev parent reply other threads:[~2024-11-25 9:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 16:28 [PATCH 0/6] 9pfs: fix fstat() after unlink() (with a Linux guest) Christian Schoenebeck
2024-02-21 14:13 ` [PATCH 1/6] tests/9p: add 'use-after-unlink' test Christian Schoenebeck
2024-11-25 8:47 ` Greg Kurz
2024-11-25 9:34 ` Christian Schoenebeck [this message]
2024-11-24 13:34 ` [PATCH 2/6] tests/9p: fix Rreaddir response name Christian Schoenebeck
2024-11-24 19:41 ` Christian Schoenebeck
2024-11-25 8:48 ` Greg Kurz
2024-11-24 14:49 ` [PATCH 3/6] tests/9p: add missing Rgetattr " Christian Schoenebeck
2024-11-24 19:42 ` Christian Schoenebeck
2024-11-25 8:51 ` Greg Kurz
2024-11-24 15:06 ` [PATCH 4/6] 9pfs: remove obsolete comment in v9fs_getattr() Christian Schoenebeck
2024-11-24 19:43 ` Christian Schoenebeck
2024-11-25 8:54 ` Greg Kurz
2024-11-24 15:50 ` [PATCH 5/6] 9pfs: fix 'Tgetattr' after unlink Christian Schoenebeck
2024-11-24 19:44 ` Christian Schoenebeck
2024-11-26 16:03 ` Christian Schoenebeck
2024-11-26 16:58 ` Greg Kurz
2024-11-24 16:05 ` [PATCH 6/6] tests/9p: also check 'Tgetattr' in 'use-after-unlink' test Christian Schoenebeck
2024-11-26 17:02 ` Greg Kurz
2024-11-25 8:45 ` [PATCH 0/6] 9pfs: fix fstat() after unlink() (with a Linux guest) Greg Kurz
2024-11-25 9:05 ` Greg Kurz
2024-11-25 10:23 ` Christian Schoenebeck
2024-11-25 11:35 ` Greg Kurz
2024-11-25 14:11 ` Christian Schoenebeck
2024-11-27 9:58 ` Christian Schoenebeck
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=1935071.n0I2rtNXNV@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.