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 17:28:04 +0900
commit8a69be3669e2ef632e0333eac0ae80fd91c3c1f3 (patch)
tree0e9000cac364aae13025c59bc3557eb667fda693 /scripts/Makefile.thinlto
parentb40cddb8dac4f9530f912f0dfe87ac4942623db0 (diff)
downloadlinux-next-8a69be3669e2ef632e0333eac0ae80fd91c3c1f3.tar.gz
linux-next-8a69be3669e2ef632e0333eac0ae80fd91c3c1f3.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