mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Alex Elder <elder@ieee.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jens Axboe <axboe@kernel.dk>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Daniel Vacek <neelx@suse.com>, Ilya Dryomov <idryomov@gmail.com>,
	Dongsheng Yang <dongsheng.yang@easystack.cn>,
	Xiubo Li <xiubli@redhat.com>,
	eahariha@linux.microsoft.com, ceph-devel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] rbd: convert timeouts to secs_to_jiffies()
Date: Mon, 3 Mar 2025 10:13:34 -0800	[thread overview]
Message-ID: <d5035d88-f714-47c2-ace6-8bd609d84633@linux.microsoft.com> (raw)
In-Reply-To: <4c4b3d6f-64b7-4ba3-8d2e-d8b1f1a03a53@ieee.org>

On 3/2/2025 9:05 AM, Alex Elder wrote:
> On 2/28/25 10:22 PM, Easwar Hariharan wrote:
>> 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)
>>
>> Change the check for range to check against HZ.
>>
>> Acked-by: Ilya Dryomov <idryomov@gmail.com>
>> Signed-off-by: Easwar Hariharan <eahariha@linux.microsoft.com>
> 
> I think what you've done in the last hunk below should not be
> done that way.  I also suggest something to the (related, but
> not part of this series) secs_to_jiffies() implementation.
> 
>> ---
>>   drivers/block/rbd.c | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
>> index faafd7ff43d6ef53110ab3663cc7ac322214cc8c..1c406b17f3cee741b7bdd9f742958b3f1d5b1bbe 100644
>> --- a/drivers/block/rbd.c
>> +++ b/drivers/block/rbd.c
>> @@ -108,7 +108,7 @@ static int atomic_dec_return_safe(atomic_t *v)
>>   #define RBD_OBJ_PREFIX_LEN_MAX    64
>>     #define RBD_NOTIFY_TIMEOUT    5    /* seconds */
>> -#define RBD_RETRY_DELAY        msecs_to_jiffies(1000)
>> +#define RBD_RETRY_DELAY        secs_to_jiffies(1)
>>     /* Feature bits */
>>   @@ -4162,7 +4162,7 @@ static void rbd_acquire_lock(struct work_struct *work)
>>           dout("%s rbd_dev %p requeuing lock_dwork\n", __func__,
>>                rbd_dev);
>>           mod_delayed_work(rbd_dev->task_wq, &rbd_dev->lock_dwork,
>> -            msecs_to_jiffies(2 * RBD_NOTIFY_TIMEOUT * MSEC_PER_SEC));
>> +            secs_to_jiffies(2 * RBD_NOTIFY_TIMEOUT));
>>       }
>>   }
>>   @@ -6283,9 +6283,9 @@ static int rbd_parse_param(struct fs_parameter *param,
>>           break;
>>       case Opt_lock_timeout:
>>           /* 0 is "wait forever" (i.e. infinite timeout) */
>> -        if (result.uint_32 > INT_MAX / 1000)
> 
> Previously, the above line was verifying that the multiplication
> done below would not overflow.  It was unrelated to whatever
> msecs_to_jiffies() did.
> 
>> +        if (result.uint32 > INT_MAX / HZ)
> 
> Here you are assuming something about what secs_to_jiffies()
> does.  It's a very reasonable assumption, but you are encoding
> this in unrelated code, which you shouldn't do.
> 
> Just do the direct conversion as you've done above:
> 
>         if (result.uint32 > INT_MAX)
> 
>>               goto out_of_range;
>> -        opt->lock_timeout = msecs_to_jiffies(result.uint_32 * 1000);
>> +        opt->lock_timeout = secs_to_jiffies(result.uint_32);
> 
> Unfortunately, secs_to_jiffies() does not implement the clamp
> operation that msecs_to_jiffies() does.  If you look at
> __msecs_to_jiffies() you see that the unsigned value provided
> is limited to MAX_JIFFY_OFFSET if it's negative when interpreted
> as a signed int (i.e., if its high bit is set).
> 
> I think the secs_to_jiffies() implementation could benefit
> from the use of an overflow check.  This might not be
> exactly right, but it gives the idea:

Fair enough, let me explore this.

@Jens, @Andrew, can you drop the rbd and libceph patches from your respective
trees while I work this out?

Thanks,
Easwar (he/him)

> 
> #define secs_to_jiffies(_secs)                    \
>     ({                            \
>         unsigned long _result;                \
>                                 \
>         if (check_mul_overflow(_secs, HZ, &_result))    \
>             _result = MAX_JIFFY_OFFSET;        \
>         (_result);                    \
>     })
> 
>                     -Alex
> 
> 
>>           break;
>>       case Opt_pool_ns:
>>           kfree(pctx->spec->pool_ns);
>>


  reply	other threads:[~2025-03-03 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01  4:22 [PATCH v4 0/2] Converge on using secs_to_jiffies() part two Easwar Hariharan
2025-03-01  4:22 ` [PATCH v4 1/2] rbd: convert timeouts to secs_to_jiffies() Easwar Hariharan
2025-03-02 17:05   ` Alex Elder
2025-03-03 18:13     ` Easwar Hariharan [this message]
2025-03-03 18:18       ` Jens Axboe
2025-03-01  4:22 ` [PATCH v4 2/2] libceph: " Easwar Hariharan
2025-03-02 17:09   ` Alex Elder

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=d5035d88-f714-47c2-ace6-8bd609d84633@linux.microsoft.com \
    --to=eahariha@linux.microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=ceph-devel@vger.kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dongsheng.yang@easystack.cn \
    --cc=elder@ieee.org \
    --cc=idryomov@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelx@suse.com \
    --cc=xiubli@redhat.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

all inboxes | Powered by JetHome®