From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v2 0/9] 9pfs: add race test suite + fix 9p2000.u dir stream race
Date: Thu, 15 Oct 2026 16:58:55 +0200 [thread overview]
Message-ID: <2852711.mvXUDI8C0e@weasel> (raw)
In-Reply-To: <cover.1791368962.git.qemu_oss@crudebyte.com>
On Wednesday, 7 October 2026 12:29:22 CEST Christian Schoenebeck wrote:
> This series adds a race test suite for 9p and fixes a race on legacy
> 9p2000(.u)'s Tread request on directories, which was uncovered by this
> new test suite.
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
/Christian
prev parent reply other threads:[~2026-10-15 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:29 [PATCH v2 0/9] 9pfs: add race test suite + fix 9p2000.u dir stream race Christian Schoenebeck
2026-10-07 10:26 ` [PATCH v2 1/9] tests/9p-client: add Txattrwalk / Rxattrwalk test client functions Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 2/9] tests/9p-race: add 9p race test suite (race FID-path mutations) Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 3/9] tests/9p-client: add Rerror function (legacy 9p2000.u) Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 4/9] tests/9p-client: add Tstat / Rstat test client functions Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 5/9] tests/9p-race: add Treaddir race test Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 6/9] hw/9pfs: fix dirent stream protection for legacy (9p2000.u) Tread Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 7/9] tests/9p-client: add Tcreate / Rcreate test client functions Christian Schoenebeck
2026-10-07 10:27 ` [PATCH v2 8/9] tests/9p-client: track the negotiated 9p version for session Christian Schoenebeck
2026-10-07 10:28 ` [PATCH v2 9/9] tests/9p-race: add Tread-on-dir race test Christian Schoenebeck
2026-10-15 14:58 ` 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=2852711.mvXUDI8C0e@weasel \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox