From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
jack@suse.cz, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, hughd@google.com,
linux-ext4@vger.kernel.org, tytso@mit.edu, linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] symlink length caching
Date: Tue, 3 Feb 2026 15:13:09 +0100 [thread overview]
Message-ID: <20260203-reibt-bestnote-7da2affa6e26@brauner> (raw)
In-Reply-To: <20260203042052.GE3183987@ZenIV>
On Tue, Feb 03, 2026 at 04:20:52AM +0000, Al Viro wrote:
> On Thu, Nov 21, 2024 at 01:34:44PM +0100, Christian Brauner wrote:
>
> > [1/3] vfs: support caching symlink lengths in inodes
> > https://git.kernel.org/vfs/vfs/c/5cbb3c7e0051
> > [2/3] ext4: use inode_set_cached_link()
> > https://git.kernel.org/vfs/vfs/c/740456f67017
> > [3/3] tmpfs: use inode_set_cached_link()
> > https://git.kernel.org/vfs/vfs/c/30071e02c163
>
> _Very_ belated note: that needs D/f/porting.rst chunk that would cover
> readlink_copy() calling conventions change.
No probs. I'll put something in there in a second.
next prev parent reply other threads:[~2026-02-03 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:20 Mateusz Guzik
2024-11-20 11:20 ` [PATCH v3 1/3] vfs: support caching symlink lengths in inodes Mateusz Guzik
2024-11-21 10:12 ` Christian Brauner
2024-11-21 13:56 ` Mateusz Guzik
2024-11-22 1:56 ` Dave Chinner
2024-11-20 11:20 ` [PATCH v3 2/3] ext4: use inode_set_cached_link() Mateusz Guzik
2024-11-21 11:58 ` Jan Kara
2024-11-20 11:20 ` [PATCH v3 3/3] tmpfs: " Mateusz Guzik
2024-11-21 11:59 ` Jan Kara
2024-11-21 12:34 ` [PATCH v3 0/3] symlink length caching Christian Brauner
2026-02-03 4:20 ` Al Viro
2026-02-03 14:13 ` Christian Brauner [this message]
2024-11-21 14:16 ` Jeff Layton
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=20260203-reibt-bestnote-7da2affa6e26@brauner \
--to=brauner@kernel.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=tytso@mit.edu \
--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