mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: Hongling Zeng <zenghongling@kylinos.cn>,
	linkinjeon@kernel.org, hyc.lee@gmail.com
Cc: ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
	zhongling0719@126.com, stable@vger.kernel.org
Subject: Re: [PATCH] ntfs: fix undefined behavior in mft/index record size calculation
Date: Wed, 26 Aug 2026 12:02:53 +0800	[thread overview]
Message-ID: <e71a505f-1113-4268-930f-bfb22d2af27f@163.com> (raw)
In-Reply-To: <20260825095405.858623-1-zenghongling@kylinos.cn>


在 2026/8/25 17:54, Hongling Zeng 写道:
> The boot sector validation allows clusters_per_mft_record and
> clusters_per_index_record to range from 0xE1 (-31) to 0xF7 (-9) when
> interpreted as signed values. When these are used as negative shift
> counts in expressions like `1 << -clusters_per_mft_record`, values
> like 0xE1 cause `1 << 31`, which shifts into the sign bit of a 32-bit
> signed integer, resulting in undefined behavior.
> 
> Fix by using unsigned shift (1U << ...) instead of signed shift.
> This prevents undefined behavior while preserving the full valid
> range of negative values (-31 to -9) that may appear in NTFS boot
> sectors.
> 
> The encoding scheme uses negative values to represent record sizes
> smaller than cluster_size: -log2(record_size). Common values include
> -10 (1024 bytes) for mft_record_size and -12 (4096 bytes) for
> index_record_size.
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hongling Zeng <zenghongling@kylinos.cn>
> ---
>   fs/ntfs/super.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/ntfs/super.c b/fs/ntfs/super.c
> index 30481e5d5dd4..a1813093222b 100644
> --- a/fs/ntfs/super.c
> +++ b/fs/ntfs/super.c
> @@ -695,7 +695,7 @@ static bool parse_ntfs_boot_sector(struct ntfs_volume *vol,
>   		 * = -log2(mft_record_size) bytes. mft_record_size normaly is
>   		 * 1024 bytes, which is encoded as 0xF6 (-10 in decimal).
>   		 */
> -		vol->mft_record_size = 1 << -clusters_per_mft_record;
> +		vol->mft_record_size = 1U << -clusters_per_mft_record;
>   	vol->mft_record_size_mask = vol->mft_record_size - 1;
>   	vol->mft_record_size_bits = ffs(vol->mft_record_size) - 1;
>   	ntfs_debug("vol->mft_record_size = %i (0x%x)", vol->mft_record_size,
> @@ -732,7 +732,7 @@ static bool parse_ntfs_boot_sector(struct ntfs_volume *vol,
>   		 * index_record_size normaly equals 4096 bytes, which is
>   		 * encoded as 0xF4 (-12 in decimal).
>   		 */
> -		vol->index_record_size = 1 << -clusters_per_index_record;
> +		vol->index_record_size = 1U << -clusters_per_index_record;
>   	vol->index_record_size_mask = vol->index_record_size - 1;
>   	vol->index_record_size_bits = ffs(vol->index_record_size) - 1;
>   	ntfs_debug("vol->index_record_size = %i (0x%x)",

Looks good to me.
Reviewed-by: Baolin Liu <liubaolin@kylinos.cn>


  reply	other threads:[~2026-08-26  4:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  9:54 Hongling Zeng
2026-08-26  4:02 ` liubaolin [this message]
2026-08-26 11:29 ` Namjae Jeon

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=e71a505f-1113-4268-930f-bfb22d2af27f@163.com \
    --to=liubaolin12138@163.com \
    --cc=hyc.lee@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=zenghongling@kylinos.cn \
    --cc=zhongling0719@126.com \
    /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®