mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2025-01-04 04:02:26 +00:00
9ed50b8231
Fast symlink can be used if the on-disk symlink data is stored
in the same block as the on-disk inode, so we don’t need to trigger
another I/O for symlink data. However, currently fs correction could be
reported _incorrectly_ if inode xattrs are too large.
In fact, these should be valid images although they cannot be handled as
fast symlinks.
Many thanks to Colin for reporting this!
Reported-by: Colin Walters <walters@verbum.org>
Reported-by: https://honggfuzz.dev/
Link: https://lore.kernel.org/r/bb2dd430-7de0-47da-ae5b-82ab2dd4d945@app.fastmail.com
Fixes:
|
||
---|---|---|
.. | ||
compress.h | ||
data.c | ||
decompressor_deflate.c | ||
decompressor_lzma.c | ||
decompressor_zstd.c | ||
decompressor.c | ||
dir.c | ||
erofs_fs.h | ||
fscache.c | ||
inode.c | ||
internal.h | ||
Kconfig | ||
Makefile | ||
namei.c | ||
super.c | ||
sysfs.c | ||
xattr.c | ||
xattr.h | ||
zdata.c | ||
zmap.c | ||
zutil.c |