From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pedro Falcato <pedro.falcato@gmail.com>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Eric Van Hensbergen <ericvh@kernel.org>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: [GIT PULL] 9p fixes for 6.12-rc4
Date: Sat, 19 Oct 2024 08:51:44 +0900 [thread overview]
Message-ID: <ZxL0kMXLDng3Kw_V@codewreck.org> (raw)
The following changes since commit 98f7e32f20d28ec452afb208f9cffc08448a2652:
Linux 6.11 (2024-09-15 16:57:56 +0200)
are available in the Git repository at:
https://github.com/martinetd/linux tags/9p-for-6.12-rc4
for you to fetch changes up to 79efebae4afc2221fa814c3cae001bede66ab259:
9p: Avoid creating multiple slab caches with the same name (2024-09-23 05:51:27 +0900)
----------------------------------------------------------------
Mashed-up update that I sat on too long:
- fix for multiple slabs created with the same name
- enable multipage folios
- theorical fix to also look for opened fids by inode if none
was found by dentry
----------------------------------------------------------------
David Howells (1):
9p: Enable multipage folios
Dominique Martinet (1):
9p: v9fs_fid_find: also lookup by inode if not found dentry
Pedro Falcato (1):
9p: Avoid creating multiple slab caches with the same name
fs/9p/fid.c | 5 ++---
fs/9p/vfs_inode.c | 1 +
net/9p/client.c | 10 +++++++++-
3 files changed, 12 insertions(+), 4 deletions(-)
--
Dominique Martinet | Asmadeus
next reply other threads:[~2024-10-18 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 23:51 Dominique Martinet [this message]
2024-10-19 16:01 ` [GIT PULL] 9p fixes for 6.12-rc4 pr-tracker-bot
2024-10-23 16:56 ` Andrii Nakryiko
2024-10-23 23:23 ` Dominique Martinet
2024-10-23 23:37 ` Andrii Nakryiko
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=ZxL0kMXLDng3Kw_V@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=pedro.falcato@gmail.com \
--cc=regressions@leemhuis.info \
--cc=torvalds@linux-foundation.org \
--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