From: Andi Kleen <ak@linux.intel.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: Winston Wen <wentao@uniontech.com>, linux-ext4@vger.kernel.org
Subject: Re: Inquiry: Possible built-in support for longer filenames in ext4 (beyond 256 bytes)
Date: Fri, 12 Dec 2025 10:10:36 -0800 [thread overview]
Message-ID: <87pl8jzi3n.fsf@linux.intel.com> (raw)
In-Reply-To: <20251210232459.GD42106@macsyma.local> (Theodore Tso's message of "Thu, 11 Dec 2025 08:24:59 +0900")
"Theodore Tso" <tytso@mit.edu> writes:
>
> Well, extended attributes won't work, because xattrs are associated
> with the inode, not the directory entry. So you need to handle cases
> where the file has multiple hard links. And if you are doing a lookup
> by long file name, there's a chicken and egg problem; you can't match
> against the full filename until you read the xattr, and you can't do
> that until you've lookup.
Perhaps you could use xattrs on the directory inode to store the longer
names, or the overflow.
One problem is that they may need to be big, exceeding xattr
limits, but perhaps some total limit on the longer file names
would be acceptable.
-Andi
next prev parent reply other threads:[~2025-12-12 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 7:02 Inquiry: Possible built-in support for longer filenames in ext4 (beyond 256 bytes) Winston Wen
2025-12-10 9:05 ` Theodore Tso
2025-12-10 9:32 ` Winston Wen
2025-12-10 23:24 ` Theodore Tso
2025-12-11 1:21 ` Winston Wen
2025-12-12 18:10 ` Andi Kleen [this message]
2025-12-12 23:35 ` Theodore Tso
2025-12-15 15:04 ` Andi Kleen
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=87pl8jzi3n.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wentao@uniontech.com \
/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