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: Sat, 13 Jan 2018 19:49:16 +0000 [thread overview]
Message-ID: <bug-198301-13602-wv0g5CoUfT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198301-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198301
Josh Johnston (josh.johnston@hotmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |josh.johnston@hotmail.com
--- Comment #2 from Josh Johnston (josh.johnston@hotmail.com) ---
Created attachment 273589
--> https://bugzilla.kernel.org/attachment.cgi?id=273589&action=edit
Proposed patch
Here's a proposed patch. When the symlink's path length is longer than a
block, it uses the existing code to fall back on a slow symlink. This is the
better behavior, rather than throwing an error.
Block size should only be a limitation on the path if using a fast symlink,
which includes the path in the inode. More info on fast/slow symlinks at:
https://unix.stackexchange.com/questoins/147535/fast-and-slow-symlinks
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-01-13 19:49 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 [this message]
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-wv0g5CoUfT@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.