From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: <linux-nfs@vger.kernel.org>, Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] NFSv4: prevent integer overflow while calling nfs4_set_lease_period()
Date: Wed, 2 Jul 2025 19:47:36 +0300 [thread overview]
Message-ID: <8244b3f4-ea69-46ee-9ba2-6711f516f00b@omp.ru> (raw)
In-Reply-To: <f769ad67-fc6b-4101-8bdc-8b41eba73a21@omp.ru>
On 7/1/25 11:35 PM, Sergey Shtylyov wrote:
> The nfs_client::cl_lease_time field (as well as the jiffies variable it's
> used with) is declared as *unsigned long*, which is 32-bit type on 32-bit
> arches and 64-bit type on 64-bit arches. When nfs4_set_lease_period() that
> sets nfs_client::cl_lease_time is called, 32-bit nfs_fsinfo::lease_time
> field is multiplied by HZ -- that might overflow before being implicitly
> cast to *unsigned long*. Actually, there's no need to multiply by HZ at all
> the call sites of nfs4_set_lease_period() -- it makes more sense to do that
> once, inside that function, calling check_mul_overflow() and capping result
> at ULONG_MAX on actual overflow...
>
> Found by Linux Verification Center (linuxtesting.org) with the Svace static
> analysis tool.
>
> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
> Cc: stable@vger.kernel.org
>
> ---
> The patch is against the master branch of Trond Myklebust's linux-nfs.git repo.
>
> Changes in version 2:
> - made use of check_mul_overflow() instead of mul_u32_u32();
> - capped the multiplication result at ULONG_MAX instead of returning -ERANGE,
> keeping nfs4_set_lease_period() *void*;
> - rewrote the patch description accordingly.
Forgot to say that I had to adjust the patch description to make it clear
that the overflow happens on 64-bit arches as well...
[...]
MBR, Sergey
next prev parent reply other threads:[~2025-07-02 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 20:35 [PATCH v2] NFSv4: prevent integer overflow while calling nfs4_set_lease_period() Sergey Shtylyov
2025-07-02 16:47 ` Sergey Shtylyov [this message]
2025-07-25 20:19 ` Sergey Shtylyov
2025-07-25 23:39 ` Trond Myklebust
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=8244b3f4-ea69-46ee-9ba2-6711f516f00b@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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