From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Wentao Liang <vulab@iscas.ac.cn>
Subject: [PATCH 0/2] nilfs2: improve sanity checks in dirty state propagation
Date: Tue, 29 Apr 2025 02:37:06 +0900 [thread overview]
Message-ID: <20250428173808.6452-1-konishi.ryusuke@gmail.com> (raw)
Hi Andrew, please queue this series for the next merge cycle.
This fixes one missed check for block mapping anomalies and one improper
return of an error code during a preparation step for log writing,
thereby improving checking for filesystem corruption on writeback.
Thanks,
Ryusuke Konishi
Ryusuke Konishi (1):
nilfs2: do not propagate ENOENT error from nilfs_btree_propagate()
Wentao Liang (1):
nilfs2: Add pointer check for nilfs_direct_propagate()
fs/nilfs2/btree.c | 4 +++-
fs/nilfs2/direct.c | 3 +++
2 files changed, 6 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-04-28 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 17:37 Ryusuke Konishi [this message]
2025-04-28 17:37 ` [PATCH 1/2] nilfs2: Add pointer check for nilfs_direct_propagate() Ryusuke Konishi
2025-04-28 17:37 ` [PATCH 2/2] nilfs2: do not propagate ENOENT error from nilfs_btree_propagate() Ryusuke Konishi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250428173808.6452-1-konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®