From: Michael Grzeschik <mgr@pengutronix.de>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: v9fs@lists.linux.dev, ericvh@kernel.org, lucho@ionkov.net,
linux_oss@crudebyte.com, Pierre Barre <pierre@barre.sh>,
sandeen@redhat.com, Remi Pommarel <repk@triplefau.lt>,
David Howells <dhowells@redhat.com>
Subject: Re: 9p patches in flight recap/what did I miss
Date: Thu, 16 Apr 2026 11:56:03 +0200 [thread overview]
Message-ID: <aeCyM2ReRaofLO2h@pengutronix.de> (raw)
In-Reply-To: <aeBToj14IBI6jh6Q@codewreck.org>
[-- Attachment #1: Type: text/plain, Size: 3210 bytes --]
On Thu, Apr 16, 2026 at 12:12:34PM +0900, Dominique Martinet wrote:
>Hi all,
>
>This is mostly for myself as I can't keep up, please tell me if I'm
>missing anything obvious.
>
>I have these queued for 7.1-rc1 (will send early next week to Linus)
>
>https://lore.kernel.org/r/20260225135745.351984-1-sashal@kernel.org/
>* 0fd76f1be20d 9p: fix memory leak in v9fs_init_fs_context error path
>https://lore.kernel.org/r/0ddc72da-d196-4f01-8755-0086f670e779@app.fastmail.com/
>* da2346a48a5a 9p: fix access mode flags being ORed instead of replaced
>https://lore.kernel.org/r/20260315190633.73536-1-xaum.io@gmail.com/
>* 890d56964c62 9p: document missing enum values in kernel-doc comments
>https://lore.kernel.org/r/20260324153023.86853-2-ericterminal@gmail.com/
>* 72cb9ee4f6d8 9p/trans_xen: make cleanup idempotent after dataring alloc errors
>* 8fc518e489c1 9p/trans_xen: replace simple_strto* with kstrtouintq
>
>I have these queued for 7.2
>
>https://lore.kernel.org/r/551c057c5dbcc83f19b9c8a3b508bd971598f657.1774380535.git.repk@triplefau.lt/
>* fabe6e8af53a 9p: Cache negative dentries for lookup performance
>* 2e624a12ba29 9p: Add mount option for negative dentry cache retention
>* 060ba5a058cb 9p: Set default negative dentry retention time for cache=loose
>* 47a37d360868 9p: Enable symlink caching in page cache
>
>And these that need some work/help sorting out
>- usb fixes 20260319-9pfixes-v1-0-c977a7433185@pengutronix.de
>** I don't have the bandwidth for such a big rework, happy to just trust
>Michael here given I can't test usb...
I just worked in some feedback from sashiko. And sashiko really got some
points. Although I have embedded devices to further test this, I am
about to leave Pengutronix in the end of April I don't know if I will be
able to solve all the obstacles in the series until then.
>- writeback corruption 20251227083751.715152-1-pierre@barre.sh
>** David sent another patch but honestly it's too complex for a quick
>review, my gut feeling is to prefer Pierre's simpler approach first and
>take the time to iterate (if we ever find time to...), but I just
>haven't the time to check even that.
>- lifting virtio msize limit
>cover.1657920926.git.linux_oss@crudebyte.com and/or virtio buffer
>iteration 20251214-virtio_trans_iter-v2-1-f7f7072e8c15@codewreck.org
>** Once again ENOTIME stikes so I didn't check, but do your patches also
>address the invalid access problem? Should we get Chris to test with
>your patches?
>I still think it's a shame to duplicate all this code and it should be
>possible to do a bit better, but I agree improving sg_table is an
>elephant I don't want to fight...
>
>
>Thank you all,
>
>by the way if anyone wants to take over for (at least) the next few
>cycles I wouldn't mind at all, having a shiny new baby and a jealous 3yo
>doesn't help :p
>--
>Dominique
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-04-16 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 3:12 9p patches in flight recap/what did I miss Dominique Martinet
2026-04-16 9:56 ` Michael Grzeschik [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=aeCyM2ReRaofLO2h@pengutronix.de \
--to=mgr@pengutronix.de \
--cc=asmadeus@codewreck.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=pierre@barre.sh \
--cc=repk@triplefau.lt \
--cc=sandeen@redhat.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