diff options
| author | Namjae Jeon <linkinjeon@kernel.org> | 2026-04-22 11:56:12 +0900 |
|---|---|---|
| committer | Namjae Jeon <linkinjeon@kernel.org> | 2026-04-22 19:05:07 +0900 |
| commit | 36ee1313199b7f16bf963c6ac0241861585125d9 (patch) | |
| tree | 1b22487eaf912311bf05c220d355264a72c82010 /include/linux/stackprotector.h | |
| parent | 6e0152c75d70725add4cef3b1cb10abc6efa6ad9 (diff) | |
ntfs: use page allocation for resident attribute inline data
The current kmemdup() based allocation for IOMAP_INLINE can result in
inline_data pointer having a non-zero page offset. This causes
iomap_inline_data_valid() to fail the check:
iomap->length <= PAGE_SIZE - offset_in_page(iomap->inline_data)
and triggers the kernel BUG at fs/iomap/buffered-io.c:1061.
This particularly affects workloads with frequent small file access
(e.g. Firefox Nightly profile on NTFS with bind mount) when using the
new ntfs. This fix this by allocating a full page with alloc_page() so that
page_address() always returns a page-aligned address.
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Diffstat (limited to 'include/linux/stackprotector.h')
0 files changed, 0 insertions, 0 deletions
