public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 198301] ext4 fails to create symlink if target length is greater than block size (but smaller than PATH_MAX)
Date: Sun, 14 Jan 2018 00:16:34 +0000	[thread overview]
Message-ID: <bug-198301-13602-lXUh7ZKLl7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198301-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=198301

Eric Biggers (ebiggers3@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebiggers3@gmail.com

--- Comment #7 from Eric Biggers (ebiggers3@gmail.com) ---
> The strange side effect of this bug is that one can not link to every file in
> a file system with a block size of e.g. 1k while PATH_MAX is 4k.

Note that you cannot necessarily link to every file in the filesystem even with
a 4k block size, since the absolute path to a file can be over PATH_MAX. 
PATH_MAX is a limit on the path string passed to syscalls, not a limit on the
directory structure.  By using cwd-relative paths, fd-relative paths, chroots,
or bind mounts, you can create a directory structure that is much deeper than
PATH_MAX.  None of the major Linux filesystems enforce a directory depth limit,
as far as I know -- and even if one did, it could still be mounted at a
mountpoint whose absolute path is already PATH_MAX, or close to it.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2018-01-14  0:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 15:34 [Bug 198301] New: ext4 fails to create symlink if target length is greater than block size (but smaller than PATH_MAX) bugzilla-daemon
2018-01-09  9:12 ` [Bug 198301] " bugzilla-daemon
2018-01-13 19:49 ` bugzilla-daemon
2018-01-13 23:22 ` bugzilla-daemon
2018-01-13 23:30 ` bugzilla-daemon
2018-01-14  0:05 ` bugzilla-daemon
2018-01-14  0:06 ` bugzilla-daemon
2018-01-14  0:16 ` bugzilla-daemon [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=bug-198301-13602-lXUh7ZKLl7@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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