On Fri, Dec 02, 2016 at 12:14:22PM -0500, Theodore Ts'o wrote: > On a filesystem with no journal, a symlink longer than about 32 > characters (exact length depending on padding for encryption) could not > be followed or read immediately after being created in an encrypted > directory. This happened because when the symlink data went through the > delayed allocation path instead of the journaling path, the symlink was > incorrectly detected as a "fast" symlink rather than a "slow" symlink > until its data was written out. > > To fix this, disable delayed allocation for symlinks, since there is > no benefit for delayed allocation anyway. > Looks good to me. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
