public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Winston Wen <wentao@uniontech.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Inquiry: Possible built-in support for longer filenames in ext4 (beyond 256 bytes)
Date: Wed, 10 Dec 2025 18:05:36 +0900	[thread overview]
Message-ID: <20251210090536.GB42106@macsyma.local> (raw)
In-Reply-To: <63C71AFEB9EEBDC8+20251210145935.72a6f028@winn-pc>

On Wed, Dec 10, 2025 at 03:02:11PM +0800, Winston Wen wrote:
> We are aware that workarounds like wrapfs can be used to support longer
> filenames, but in practice, this approach is not ideal for seamless
> user experience. We are therefore curious whether it would be feasible
> to implement built-in support for longer filenames in ext4 itself.

I don't think wrapfs can be used to support logner file names, because
the limitation is quite fundamental.  For example, the glibc
definition of struct dirent (which is returned by the readdir() system
call) is as follows (from the man readdir page):

           struct dirent {
               ino_t          d_ino;       /* Inode number */
               off_t          d_off;       /* Not an offset; see below */
               unsigned short d_reclen;    /* Length of this record */
               unsigned char  d_type;      /* Type of file; not supported
                                              by all filesystem types */
               char           d_name[256]; /* Null-terminated filename */
           };

So how you might store the longer file name isn't really going to
help, the problem goes far beyond the question of where this might be
stored on the file system.

					- Ted

  reply	other threads:[~2025-12-10  9:05 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 [this message]
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
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=20251210090536.GB42106@macsyma.local \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --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