From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Aldo Ariel Panzardo <qwe.aldo@gmail.com>,
Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] nilfs2: validate file block counts during recovery
Date: Tue, 15 Sep 2026 12:46:54 -0700 [thread overview]
Message-ID: <5a7a00bdaa378af13ca6b3dfe58992188557493d.camel@dubeyko.com> (raw)
In-Reply-To: <20260915111351.2726334-1-qwe.aldo@gmail.com>
On Tue, 2026-09-15 at 08:13 -0300, Aldo Ariel Panzardo wrote:
> nilfs_scan_dsync_log() trusts the block counts in each on-disk file
> information entry. If fi_ndatablk is greater than fi_nblocks, the
> data
> block loop can consume excessive summary entries and the later
> subtraction
> used to derive the number of node blocks underflows.
>
> Reject inconsistent file information entries before consuming their
> block
> information.
>
> Fixes: 0f3e1c7f23f8 ("nilfs2: recovery functions")
> Cc: stable@vger.kernel.org
> Signed-off-by: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
> ---
> fs/nilfs2/recovery.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/fs/nilfs2/recovery.c b/fs/nilfs2/recovery.c
> index 4d5a6aa521..6e4e0cf4cc 100644
> --- a/fs/nilfs2/recovery.c
> +++ b/fs/nilfs2/recovery.c
> @@ -322,6 +322,7 @@ static void nilfs_skip_summary_info(struct
> the_nilfs *nilfs,
> *
> * Return: 0 on success, or one of the following negative error
> codes on
> * failure:
> + * * %-EINVAL - Invalid block counts in a file information entry.
> * * %-EIO - I/O error.
> * * %-ENOMEM - Insufficient memory available.
> */
> @@ -359,6 +360,10 @@ static int nilfs_scan_dsync_log(struct the_nilfs
> *nilfs, sector_t start_blocknr,
> ino = le64_to_cpu(finfo->fi_ino);
> nblocks = le32_to_cpu(finfo->fi_nblocks);
> ndatablk = le32_to_cpu(finfo->fi_ndatablk);
> + if (ndatablk > nblocks) {
> + err = -EINVAL;
It sounds like -EIO because we have corrupted state of on-disk
metadata.
Thanks,
Slava.
> + goto out;
> + }
> nnodeblk = nblocks - ndatablk;
>
> while (ndatablk-- > 0) {
next prev parent reply other threads:[~2026-09-15 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 11:13 Aldo Ariel Panzardo
2026-09-15 19:46 ` Viacheslav Dubeyko [this message]
2026-09-15 19:56 ` Aldo Ariel Panzardo
2026-09-15 19:57 ` [PATCH v2] " Aldo Ariel Panzardo
2026-09-16 19:10 ` Viacheslav Dubeyko
2026-09-18 15:44 ` [PATCH] " Ryusuke Konishi
2026-09-18 19:33 ` Viacheslav Dubeyko
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=5a7a00bdaa378af13ca6b3dfe58992188557493d.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=qwe.aldo@gmail.com \
--cc=stable@vger.kernel.org \
/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®