From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Miguel Ojeda <ojeda@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
eahariha@linux.microsoft.com, stable@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] jiffies: Cast to unsigned long for secs_to_jiffies() conversion
Date: Thu, 30 Jan 2025 11:25:10 -0800 [thread overview]
Message-ID: <085b4f6b-0399-4b77-a2af-9bf2e19e5f62@linux.microsoft.com> (raw)
In-Reply-To: <20250130184320.69553-1-eahariha@linux.microsoft.com>
On 1/30/2025 10:43 AM, Easwar Hariharan wrote:
> While converting users of msecs_to_jiffies(), lkp reported that some
> range checks would always be true because of the mismatch between the
> implied int value of secs_to_jiffies() vs the unsigned long
> return value of the msecs_to_jiffies() calls it was replacing. Fix this
> by casting secs_to_jiffies() values as unsigned long.
>
> Fixes: b35108a51cf7ba ("jiffies: Define secs_to_jiffies()")
> CC: stable@vger.kernel.org # 6.12+
Sorry, this should be 6.13+ since secs_to_jiffies() was introduced in
6.13-rc1, not 6.12-rc1. I was mislead by git describe output. Let me
send this as a v2.
Thanks,
Easwar (he/him)
next prev parent reply other threads:[~2025-01-30 19:25 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 [this message]
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
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=085b4f6b-0399-4b77-a2af-9bf2e19e5f62@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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