[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240821154627.11848-1-konishi.ryusuke@gmail.com>
Date: Thu, 22 Aug 2024 00:46:22 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-nilfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] nilfs2: prevent unexpected ENOENT propagation
Hi Andrew,
please add this series to the queue for the next cycle.
This series fixes potential issues where the result code -ENOENT,
which is returned internally when a metadata file operation encouters
a hole block, is exposed to user space without being properly handled.
Several issues with the same cause leading to hangs or WARN_ON check
failures have been reported by syzbot and fixed each time in the past.
This collectively fixes the missing -ENOENT conversions that do not
cause stability issues and are not covered by syzbot.
Thanks,
Ryusuke Konishi
Ryusuke Konishi (5):
nilfs2: treat missing sufile header block as metadata corruption
nilfs2: treat missing cpfile header block as metadata corruption
nilfs2: do not propagate ENOENT error from sufile during recovery
nilfs2: do not propagate ENOENT error from sufile during GC
nilfs2: do not propagate ENOENT error from nilfs_sufile_mark_dirty()
fs/nilfs2/cpfile.c | 22 ++++++++-------
fs/nilfs2/recovery.c | 11 +++++++-
fs/nilfs2/segment.c | 64 ++++++++++++++++++++++++++++++++++++++------
fs/nilfs2/sufile.c | 32 +++++++++++++++++-----
4 files changed, 104 insertions(+), 25 deletions(-)
--
2.34.1
Powered by blists - more mailing lists