From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Rand Deeb <rand.sec96@gmail.com>,
jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: deeb.rand@confident.ru, lvc-project@linuxtesting.org,
voskresenski.stanislav@confident.ru
Subject: Re: [PATCH] fs/jfs: cast inactags to s64 to prevent potential overflow
Date: Thu, 20 Feb 2025 09:38:39 -0600 [thread overview]
Message-ID: <f1c5490e-8d14-416f-bfbc-0041263870f5@oracle.com> (raw)
In-Reply-To: <20250220094349.1685195-1-rand.sec96@gmail.com>
On 2/20/25 3:43AM, Rand Deeb wrote:
> The expression "inactags << bmp->db_agl2size" in the function
> dbFinalizeBmap() is computed using int operands. Although the
> values (inactags and db_agl2size) are derived from filesystem
> parameters and are usually small, there is a theoretical risk that
> the shift could overflow a 32-bit int if extreme values occur.
>
> According to the C standard, shifting a signed 32-bit int can lead
> to undefined behavior if the result exceeds its range. In our
> case, an overflow could miscalculate free blocks, potentially
> leading to erroneous filesystem accounting.
>
> To ensure the arithmetic is performed in 64-bit space, we cast
> "inactags" to s64 before shifting. This defensive fix prevents any
> risk of overflow and complies with kernel coding best practices.
Looks good. I'll add this to jfs-next.
Shaggy
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Rand Deeb <rand.sec96@gmail.com>
> ---
> fs/jfs/jfs_dmap.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c
> index f9009e4f9ffd..f89f07c9580e 100644
> --- a/fs/jfs/jfs_dmap.c
> +++ b/fs/jfs/jfs_dmap.c
> @@ -3666,8 +3666,8 @@ void dbFinalizeBmap(struct inode *ipbmap)
> * system size is not a multiple of the group size).
> */
> inactfree = (inactags && ag_rem) ?
> - ((inactags - 1) << bmp->db_agl2size) + ag_rem
> - : inactags << bmp->db_agl2size;
> + (((s64)inactags - 1) << bmp->db_agl2size) + ag_rem
> + : ((s64)inactags << bmp->db_agl2size);
>
> /* determine how many free blocks are in the active
> * allocation groups plus the average number of free blocks
prev parent reply other threads:[~2025-02-20 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 9:43 Rand Deeb
2025-02-20 15:38 ` Dave Kleikamp [this message]
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=f1c5490e-8d14-416f-bfbc-0041263870f5@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=deeb.rand@confident.ru \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=rand.sec96@gmail.com \
--cc=voskresenski.stanislav@confident.ru \
/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®