From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: eahariha@linux.microsoft.com, Frank.Li@nxp.com,
James.Bottomley@HansenPartnership.com, Julia.Lawall@inria.fr,
Shyam-sundar.S-k@amd.com, akpm@linux-foundation.org,
axboe@kernel.dk, broonie@kernel.org, cassel@kernel.org,
cem@kernel.org, ceph-devel@vger.kernel.org, clm@fb.com,
cocci@inria.fr, dick.kennedy@broadcom.com, djwong@kernel.org,
dlemoal@kernel.org, dongsheng.yang@easystack.cn,
dri-devel@lists.freedesktop.org, dsterba@suse.com,
festevam@gmail.com, hch@lst.de, hdegoede@redhat.com,
hmh@hmh.eng.br, ibm-acpi-devel@lists.sourceforge.net,
idryomov@gmail.com, ilpo.jarvinen@linux.intel.com,
imx@lists.linux.dev, james.smart@broadcom.com, jgg@ziepe.ca,
josef@toxicpanda.com, kalesh-anakkur.purayil@broadcom.com,
kbusch@kernel.org, kernel@pengutronix.de, leon@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-pm@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-sound@vger.kernel.org, linux-spi@vger.kernel.org,
linux-xfs@vger.kernel.org, martin.petersen@oracle.com,
nicolas.palix@imag.fr, ogabbay@kernel.org, perex@perex.cz,
platform-driver-x86@vger.kernel.org, s.hauer@pengutronix.de,
sagi@grimberg.me, selvin.xavier@broadcom.com,
shawnguo@kernel.org, sre@kernel.org, tiwai@suse.com,
xiubli@redhat.com, yaron.avizrat@intel.com
Subject: Re: [PATCH v3 06/16] rbd: convert timeouts to secs_to_jiffies()
Date: Tue, 25 Feb 2025 16:02:42 -0800 [thread overview]
Message-ID: <df0c2400-147c-4104-a2e6-d1038ff31524@linux.microsoft.com> (raw)
In-Reply-To: <e53d7586-b278-4338-95a2-fa768d5d8b5e@wanadoo.fr>
On 2/25/2025 1:09 PM, Christophe JAILLET wrote:
> Le 25/02/2025 à 21:17, Easwar Hariharan a écrit :
>> Commit b35108a51cf7 ("jiffies: Define secs_to_jiffies()") introduced
>> secs_to_jiffies(). As the value here is a multiple of 1000, use
>> secs_to_jiffies() instead of msecs_to_jiffies() to avoid the multiplication
>>
>> This is converted using scripts/coccinelle/misc/secs_to_jiffies.cocci with
>> the following Coccinelle rules:
>>
>> @depends on patch@ expression E; @@
>>
>> -msecs_to_jiffies(E * 1000)
>> +secs_to_jiffies(E)
>>
>> @depends on patch@ expression E; @@
>>
>> -msecs_to_jiffies(E * MSEC_PER_SEC)
>> +secs_to_jiffies(E)
>>
>> While here, remove the no-longer necessary check for range since there's
>> no multiplication involved.
>
> I'm not sure this is correct.
> Now you multiply by HZ and things can still overflow.
>
>
> Hoping I got casting right:
>
> #define MSEC_PER_SEC 1000L
> #define HZ 100
>
>
> #define secs_to_jiffies(_secs) (unsigned long)((_secs) * HZ)
>
> static inline unsigned long _msecs_to_jiffies(const unsigned int m)
> {
> return (m + (MSEC_PER_SEC / HZ) - 1) / (MSEC_PER_SEC / HZ);
> }
>
> int main() {
>
> int n = INT_MAX - 5;
>
> printf("res = %ld\n", secs_to_jiffies(n));
> printf("res = %ld\n", _msecs_to_jiffies(1000 * n));
>
> return 0;
> }
>
>
> gives :
>
> res = -600
> res = 429496130
>
> with msec, the previous code would catch the overflow, now it overflows silently.
>
> untested, but maybe:
> if (result.uint_32 > INT_MAX / HZ)
> goto out_of_range;
>
> ?
>
> CJ
>
Thanks for the review! I was able to replicate your results, I'll try this range check
and get back.
Thanks,
Easwar (he/him)
next prev parent reply other threads:[~2025-02-26 0:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 20:17 [PATCH v3 00/16] Converge on using secs_to_jiffies() part two Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 01/16] coccinelle: misc: secs_to_jiffies: Patch expressions too Easwar Hariharan
2025-02-26 8:26 ` [cocci] " Markus Elfring
2025-02-25 20:17 ` [PATCH v3 02/16] scsi: lpfc: convert timeouts to secs_to_jiffies() Easwar Hariharan
2025-03-04 2:11 ` Martin K. Petersen
2025-02-25 20:17 ` [PATCH v3 03/16] accel/habanalabs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 04/16] ALSA: ac97: " Easwar Hariharan
2025-02-26 11:55 ` [cocci] " Markus Elfring
2025-02-25 20:17 ` [PATCH v3 05/16] btrfs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 06/16] rbd: " Easwar Hariharan
2025-02-25 21:09 ` Christophe JAILLET
2025-02-26 0:02 ` Easwar Hariharan [this message]
2025-02-26 7:28 ` Daniel Vacek
2025-02-26 8:10 ` Christophe JAILLET
2025-02-26 8:29 ` Daniel Vacek
2025-02-25 20:17 ` [PATCH v3 07/16] libceph: " Easwar Hariharan
2025-02-25 21:25 ` Christophe JAILLET
2025-02-25 20:17 ` [PATCH v3 08/16] ata: libata-zpodd: " Easwar Hariharan
2025-02-25 20:24 ` Easwar Hariharan
2025-02-26 2:00 ` Damien Le Moal
2025-02-25 20:17 ` [PATCH v3 09/16] xfs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 10/16] power: supply: da9030: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 11/16] nvme: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 12/16] spi: spi-fsl-lpspi: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 13/16] spi: spi-imx: " Easwar Hariharan
2025-02-25 20:27 ` Marc Kleine-Budde
2025-02-25 20:17 ` [PATCH v3 14/16] platform/x86/amd/pmf: " Easwar Hariharan
2025-03-21 16:08 ` Ilpo Järvinen
2025-02-25 20:17 ` [PATCH v3 15/16] platform/x86: thinkpad_acpi: " Easwar Hariharan
2025-03-21 16:06 ` Ilpo Järvinen
2025-02-25 20:17 ` [PATCH v3 16/16] RDMA/bnxt_re: " Easwar Hariharan
2025-02-25 20:30 ` (subset) [PATCH v3 00/16] Converge on using secs_to_jiffies() part two Jens Axboe
2025-02-26 11:29 ` Mark Brown
2025-02-26 20:38 ` Andrew Morton
2025-02-26 22:26 ` Mark Brown
2025-02-27 9:02 ` Carlos Maiolino
2025-02-26 16:48 ` (subset) " Mark Brown
2025-03-11 1:19 ` Martin K. Petersen
2025-03-11 2:08 ` Andrew Morton
2025-03-11 2:29 ` Martin K. Petersen
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=df0c2400-147c-4104-a2e6-d1038ff31524@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=Frank.Li@nxp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Julia.Lawall@inria.fr \
--cc=Shyam-sundar.S-k@amd.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=cassel@kernel.org \
--cc=cem@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=clm@fb.com \
--cc=cocci@inria.fr \
--cc=dick.kennedy@broadcom.com \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dongsheng.yang@easystack.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsterba@suse.com \
--cc=festevam@gmail.com \
--cc=hch@lst.de \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=idryomov@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=imx@lists.linux.dev \
--cc=james.smart@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=josef@toxicpanda.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kbusch@kernel.org \
--cc=kernel@pengutronix.de \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nicolas.palix@imag.fr \
--cc=ogabbay@kernel.org \
--cc=perex@perex.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sagi@grimberg.me \
--cc=selvin.xavier@broadcom.com \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=tiwai@suse.com \
--cc=xiubli@redhat.com \
--cc=yaron.avizrat@intel.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