From: Mateusz Guzik <mjguzik@gmail.com>
To: Christian Brauner <brauner@kernel.org>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2] fs: move fd_install() slowpath into a dedicated routine and provide commentary
Date: Wed, 12 Nov 2025 11:31:42 +0100 [thread overview]
Message-ID: <CAGudoHGTOLXH=BtiU+ja9vbdR=cMCLFTDmtHtCNa32yka6huRg@mail.gmail.com> (raw)
In-Reply-To: <20251112-mondfinsternis-rednerpult-f3efbf92cf8a@brauner>
this may get the dreaded missing arg description working, how about this on top:
diff --git a/fs/file.c b/fs/file.c
index 3f56890068aa..022e98525c65 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -641,8 +641,10 @@ void put_unused_fd(unsigned int fd)
EXPORT_SYMBOL(put_unused_fd);
-/*
- * Install a file pointer in the fd array while it is being resized.
+/**
+ * fd_install_slowpath - install a file pointer in the fd array while
it is being resized
+ * @fd: file descriptor to install the file in
+ * @file: the file to install
*
* We need to make sure our update to the array does not get lost as
the resizing
* thread can be copying the content as we modify it.
On Wed, Nov 12, 2025 at 10:30 AM Christian Brauner <brauner@kernel.org> wrote:
>
> On Mon, 10 Nov 2025 10:56:34 +0100, Mateusz Guzik wrote:
> > On stock kernel gcc 14 emits avoidable register spillage:
> > endbr64
> > call ffffffff81374630 <__fentry__>
> > push %r13
> > push %r12
> > push %rbx
> > sub $0x8,%rsp
> > [snip]
> >
> > [...]
>
> Applied to the vfs-6.19.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-6.19.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-6.19.misc
>
> [1/1] fs: move fd_install() slowpath into a dedicated routine and provide commentary
> https://git.kernel.org/vfs/vfs/c/6ecf5292038e
prev parent reply other threads:[~2025-11-12 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 9:56 [PATCH v2] fs: move fd_install() slowpath into a dedicated routine and provide commentary Mateusz Guzik
2025-11-12 9:30 ` Christian Brauner
2025-11-12 10:31 ` Mateusz Guzik [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='CAGudoHGTOLXH=BtiU+ja9vbdR=cMCLFTDmtHtCNa32yka6huRg@mail.gmail.com' \
--to=mjguzik@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).