From: Vitaliy Shevtsov <v.shevtsov@mt-integration.ru>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jani Nikula <jani.nikula@intel.com>,
<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lvc-project@linuxtesting.org>
Subject: Re: [PATCH] media: cec: avoid wraparound in timer interval calculation
Date: Sun, 2 Mar 2025 02:28:06 +0500 [thread overview]
Message-ID: <20250302022806.e66f4f2903748b9bc63289c2@mt-integration.ru> (raw)
In-Reply-To: <cff4d412-abbf-44b5-9705-ba14dff7d5d0@wanadoo.fr>
On Sat, 1 Mar 2025 12:32:30 +0100, Christophe JAILLET wrote:
> Le 01/03/2025 à 12:09, Vitaliy Shevtsov a écrit :
> > [Why]
> > The timer function code may have an integer wraparound issue. Since both
> > pin->tx_custom_low_usecs and pin->tx_custom_high_usecs can be set to up to
> > 9999999 from the user space via cec_pin_error_inj_parse_line(), this may
> > cause usecs to be overflowed when adap->monitor_pin_cnt is zero and usecs
> > is multiplied by 1000.
> >
> > [How]
> > Fix this by casting usecs to u64 when it is being converted from
> > microseconds to nanoseconds.
> >
> > Found by Linux Verification Center (linuxtesting.org) with Svace.
> >
> > Fixes: 865463fc03ed ("media: cec-pin: add error injection support")
> > Signed-off-by: Vitaliy Shevtsov <v.shevtsov@mt-integration.ru>
> > ---
> > drivers/media/cec/core/cec-pin.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/cec/core/cec-pin.c b/drivers/media/cec/core/cec-pin.c
> > index a70451d99ebc..f15ed5c67a65 100644
> > --- a/drivers/media/cec/core/cec-pin.c
> > +++ b/drivers/media/cec/core/cec-pin.c
> > @@ -1021,7 +1021,7 @@ static enum hrtimer_restart cec_pin_timer(struct hrtimer *timer)
> > pin->wait_usecs = 0;
> > pin->timer_ts = ktime_add_us(ts, usecs);
> > hrtimer_forward_now(timer,
> > - ns_to_ktime(usecs * 1000));
> > + ns_to_ktime((u64)usecs * 1000));
>
> Or maybe us_to_ktime() to be less verbose?
>
> CJ
>
That makes sense but let me check first. I will send a new one soon.
> > return HRTIMER_RESTART;
> > }
> > pin->wait_usecs = usecs - 100;
>
--
Vitaliy Shevtsov <v.shevtsov@mt-integration.ru>
prev parent reply other threads:[~2025-03-01 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 11:09 Vitaliy Shevtsov
2025-03-01 11:32 ` Christophe JAILLET
2025-03-01 21:28 ` Vitaliy Shevtsov [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=20250302022806.e66f4f2903748b9bc63289c2@mt-integration.ru \
--to=v.shevtsov@mt-integration.ru \
--cc=christophe.jaillet@wanadoo.fr \
--cc=hverkuil@xs4all.nl \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®