summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorDaeMyung Kang <charsyam@gmail.com>2026-10-13 23:58:45 +0900
committerNamjae Jeon <linkinjeon@kernel.org>2026-10-20 18:46:01 +0900
commit9b32a74f4ef52d26d68ceb3f5e492d5eac26f5fc (patch)
treec440bc50ecaa09ec88af3d274887e25ae977748f /scripts/Makefile.thinlto
parent9365c4a1357e2a5d7f1aff140429028ad292161f (diff)
downloadlinux-9b32a74f4ef52d26d68ceb3f5e492d5eac26f5fc.tar.gz
linux-9b32a74f4ef52d26d68ceb3f5e492d5eac26f5fc.zip
ntfs: report block device flush failures from fsync
ntfs_file_fsync() calls blkdev_issue_flush() after writeback but discards its return value. If the device cannot flush its write cache, fsync() reports success even though the file is not guaranteed to be durable. Reproduce this with QEMU blkdebug failing flush_to_disk with -EIO. On ntfs-next at 04fb910da2c8, a kretprobe recorded -EIO from blkdev_issue_flush() while fsync() returned 0. With this change, fsync() returns -EIO and logs the failure. The syncfs() path already reports this error. Fixes: 9c87959601e8 ("ntfs: update file operations") Cc: stable@vger.kernel.org Signed-off-by: DaeMyung Kang <charsyam@gmail.com> Reviewed-by: Baolin Liu <liubaolin@kylinos.cn> Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions