From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: eahariha@linux.microsoft.com, Jiri Slaby <jirislaby@kernel.org>,
David Laight <david.laight.linux@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Miguel Ojeda <ojeda@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] jiffies: Cast to unsigned long for secs_to_jiffies() conversion
Date: Mon, 3 Feb 2025 12:42:36 -0800 [thread overview]
Message-ID: <34a36725-6efd-43fe-9e23-19b14814b6af@linux.microsoft.com> (raw)
In-Reply-To: <47098c16-2cf3-44bc-985a-07eb2a225698@linux.microsoft.com>
On 1/31/2025 9:55 AM, Easwar Hariharan wrote:
> On 1/31/2025 12:10 AM, Geert Uytterhoeven wrote:
<snip>
>>
>> More importantly, I doubt this change is guaranteed to fix the
>> reported issue. The code[*] in retry_timeout_seconds_store() does:
>>
>> int val;
>> ...
>> if (val < -1 || val > 86400)
>> return -EINVAL;
>> ...
>> if (val != -1)
>> ASSERT(secs_to_jiffies(val) < LONG_MAX);
>>
>> As HZ is a known (rather small) constant, and val is range-checked
>> before, the compiler can still devise that the condition is always true.
>> So I think that assertion should just be removed.
>>
Following the lkp instructions to repro the issue, with this patch, the
compiler does not continue reporting that the condition is always true.
This patch is sufficient IMHO, without needing to remove the assert.
- Easwar (he/him)
prev parent reply other threads:[~2025-02-03 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 18:43 [PATCH] jiffies: Cast to unsigned long for secs_to_jiffies() conversion Easwar Hariharan
2025-01-30 19:25 ` Easwar Hariharan
2025-01-30 20:14 ` David Laight
2025-01-31 7:05 ` Jiri Slaby
2025-01-31 8:10 ` Geert Uytterhoeven
2025-01-31 17:55 ` Easwar Hariharan
2025-01-31 17:59 ` Easwar Hariharan
2025-02-03 20:42 ` Easwar Hariharan [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=34a36725-6efd-43fe-9e23-19b14814b6af@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=david.laight.linux@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luiz.von.dentz@intel.com \
--cc=ojeda@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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