From: Eric-Terminal <ericterminal@gmail.com>
To: asmadeus@codewreck.org, ericvh@kernel.org, lucho@ionkov.net
Cc: stefano.stabellini@amd.com, v9fs@lists.linux.dev,
linux-kernel@vger.kernel.org, Yufan Chen <ericterminal@gmail.com>
Subject: [PATCH v3 0/2] 9p/trans_xen: fixes and parser cleanup
Date: Tue, 24 Mar 2026 23:30:21 +0800 [thread overview]
Message-ID: <20260324153023.86853-1-ericterminal@gmail.com> (raw)
From: Yufan Chen <ericterminal@gmail.com>
Hi,
This series provides a stability fix and a parser modernization for the
9p Xen transport. It has been split from the previous mixed series
following feedback from Dominique Martinet to ease review and testing.
Patch 1 fixes a potential double-free/Oops during initialization failure
by making the dataring cleanup idempotent.
Patch 2 replaces deprecated simple_strtoul() with kstrtouint() in the
backend version parsing logic, ensuring stricter input validation.
Testing:
- Verified the series using virtme-ng.
- Patch 1: Tested error paths by forcing init failures on non-Xen systems;
dmesg confirms the new sentinel-based cleanup correctly prevents Oops.
- Patch 2: Verified with a userspace mock harness that it correctly
handles empty tokens (,,) and rejects malformed input (1abc).
v3:
- Split into a dedicated 9p/trans_xen series for v9fs.
- No functional changes since v2.
Yufan Chen (2):
9p/trans_xen: make cleanup idempotent after dataring alloc errors
9p/trans_xen: replace simple_strto* with kstrtouint
net/9p/trans_xen.c | 77 +++++++++++++++++++++++++++++++++++-------------------
1 file changed, 50 insertions(+), 27 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-24 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:30 Eric-Terminal [this message]
2026-03-24 15:30 ` [PATCH v3 1/2] 9p/trans_xen: make cleanup idempotent after dataring alloc errors Eric-Terminal
2026-04-09 1:22 ` Stefano Stabellini
2026-03-24 15:30 ` [PATCH v3 2/2] 9p/trans_xen: replace simple_strto* with kstrtouint Eric-Terminal
2026-04-09 1:30 ` Stefano Stabellini
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=20260324153023.86853-1-ericterminal@gmail.com \
--to=ericterminal@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=stefano.stabellini@amd.com \
--cc=v9fs@lists.linux.dev \
/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