From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217145] Feature request: I need very long directory and file names
Date: Mon, 06 Mar 2023 18:38:47 +0000 [thread overview]
Message-ID: <bug-217145-13602-ES9F83zYrS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217145-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217145
Andreas Dilger (adilger.kernelbugzilla@dilger.ca) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adilger.kernelbugzilla@dilg
| |er.ca
--- Comment #4 from Andreas Dilger (adilger.kernelbugzilla@dilger.ca) ---
The problem with "long filename is a description of the video" is that 1-3KiB
today may grow to 4KiB or 16KiB in the future, so fixing the filename length to
allow 1KiB or 3KiB names (out of a full 4KiB PATH_MAX) is only a short term
solution. Changing ext4 or XFS to support 3KiB or 4KiB *filenames* would be a
lot of effort for very marginal benefit.
I think the right solution is to put the "full description" into a separate
xattr on the file (which can be up to 64KiB in modern ext4) and then restrict
filenames to 255 bytes. That allows very long descriptions without impacting
interoperability.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-03-06 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 8:08 [Bug 217145] New: Feature request: I need very long directory and file names bugzilla-daemon
2023-03-06 10:15 ` [Bug 217145] " bugzilla-daemon
2023-03-06 13:00 ` bugzilla-daemon
2023-03-06 16:05 ` bugzilla-daemon
2023-03-06 18:38 ` bugzilla-daemon [this message]
2023-03-08 5:01 ` bugzilla-daemon
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=bug-217145-13602-ES9F83zYrS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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