Linux 9p file system development
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: v9fs@lists.linux.dev
Cc: ericvh@kernel.org, lucho@ionkov.net, linux_oss@crudebyte.com,
	Pierre Barre <pierre@barre.sh>,
	sandeen@redhat.com, Remi Pommarel <repk@triplefau.lt>,
	Michael Grzeschik <m.grzeschik@pengutronix.de>,
	David Howells <dhowells@redhat.com>
Subject: 9p patches in flight recap/what did I miss
Date: Thu, 16 Apr 2026 12:12:34 +0900	[thread overview]
Message-ID: <aeBToj14IBI6jh6Q@codewreck.org> (raw)

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...
- 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


             reply	other threads:[~2026-04-16  3:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16  3:12 Dominique Martinet [this message]
2026-04-16  9:56 ` 9p patches in flight recap/what did I miss Michael Grzeschik

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=aeBToj14IBI6jh6Q@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=dhowells@redhat.com \
    --cc=ericvh@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=m.grzeschik@pengutronix.de \
    --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