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 23:22:09 +0000 [thread overview]
Message-ID: <bug-198301-13602-LURnW0LddS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198301-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198301
Andreas Dilger (adilger.kernelbugzilla@dilger.ca) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adilger.kernelbugzilla@dilg
| |er.ca
--- Comment #3 from Andreas Dilger (adilger.kernelbugzilla@dilger.ca) ---
Hi Josh, did you actually test if this patch works with a symlink longer than a
single block?
The existing slow symlink code is only written to handle a single block, so
just removing the check doesn't fix that. There would also need to be a new
INCOMPATIBLE feature flag added, so that the kernel and e2fsck know that there
are symlink a longer than a single block. Otherwise they would consider the
link corrupted.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-01-13 23:22 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 [this message]
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-LURnW0LddS@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.