From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 198301] New: ext4 fails to create symlink if target length is greater than block size (but smaller than PATH_MAX)
Date: Thu, 28 Dec 2017 15:34:27 +0000 [thread overview]
Message-ID: <bug-198301-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=198301
Bug ID: 198301
Summary: ext4 fails to create symlink if target length is
greater than block size (but smaller than PATH_MAX)
Product: File System
Version: 2.5
Kernel Version: Confirmed in 4.4.103 & 4.10.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: ernst@pleiszenburg.de
Regression: No
If the block size of an ext4 file system is smaller than PATH_MAX, ext4 will
fail to create symlinks to targets with names longer than block size minus one.
Expected result: Symlinks with targets up to a length of PATH_MAX - 1 can be
created.
Actual result: Symlinks with targets up to a length of block size - 1 can be
created. If block size smaller than PATH_MAX, creating symlinks with targets
equal or greater than block size and smaller than PATH_MAX will fail with
ENAMETOOLONG.
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.
For reference, the original test & discussion which triggered this bug:
https://github.com/pjd/pjdfstest/issues/24
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-12-28 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 15:34 bugzilla-daemon [this message]
2018-01-09 9:12 ` [Bug 198301] ext4 fails to create symlink if target length is greater than block size (but smaller than PATH_MAX) 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.