From: "Bo Ye (叶波)" <Bo.Ye@mediatek.com>
To: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"rafael@kernel.org" <rafael@kernel.org>
Cc: "Yongdong Zhang (张永东)" <Yongdong.Zhang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"C Cheng (陈程)" <C.Cheng@mediatek.com>
Subject: Re: [PATCH] cpuidle: idle exit_latency overflow
Date: Thu, 16 Nov 2023 14:52:08 +0000 [thread overview]
Message-ID: <81ad0d7dcb82c6f1f49e6d0882249231682c1b6c.camel@mediatek.com> (raw)
In-Reply-To: <4118d15a-a70c-457d-8f62-d4f61f1157de@collabora.com>
On Thu, 2023-11-16 at 15:20 +0100, AngeloGioacchino Del Regno wrote:
> Il 16/11/23 14:26, Bo Ye ha scritto:
> > From: C Cheng <C.Cheng@mediatek.com>
> >
> > In detail:
> > In kernel-6.1, in the __cpuidle_driver_init function in
> > driver/cpuidle/driver.c, there is a line of code that causes
> > an overflow. The line is s->exit_latency_ns = s->exit_latency
> > * NSEC_PER_USEC. The overflow occurs because the product of an
> > int type and a constant exceeds the range of the int type.
> >
> > In C language, when you perform a multiplication operation, if
> > both operands are of int type, the multiplication operation is
> > performed on the int type, and then the result is converted to
> > the target type. This means that if the product of int type
> > multiplication exceeds the range that int type can represent,
> > an overflow will occur even if you store the result in a
> > variable of int64_t type.
> >
> > Signed-off-by: C Cheng <C.Cheng@mediatek.com>
>
> It all makes sense, but "mtk24676" is not the name of a person,
> what's going on?
Corrected, apologies for any inconvenience caused.
>
> > Signed-off-by: Bo Ye <bo.ye@mediatek.com>
>
> That's the same, you perhaps wanted to write "Bo Ye", not "bo.ye".
Corrected, apologies for any inconvenience caused. I would greatly
appreciate it if you could recommend a formatting checking tool.
If there is no auto checking tool, I will pay attention to these
formatting checks next time.
Best Regards,
Bosser
>
> Regards,
> Angelo
>
> > ---
> >
> > diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
> > index d9cda7f..631ca16 100644
> > --- a/drivers/cpuidle/driver.c
> > +++ b/drivers/cpuidle/driver.c
> > @@ -187,7 +187,7 @@
> > s->target_residency = div_u64(s-
> > >target_residency_ns, NSEC_PER_USEC);
> >
> > if (s->exit_latency > 0)
> > - s->exit_latency_ns = s->exit_latency *
> > NSEC_PER_USEC;
> > + s->exit_latency_ns = (u64)s->exit_latency *
> > NSEC_PER_USEC;
> > else if (s->exit_latency_ns < 0)
> > s->exit_latency_ns = 0;
> > else
>
>
next prev parent reply other threads:[~2023-11-16 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:26 [PATCH] cpuidle: idle exit_latency overflow Bo Ye
2023-11-16 14:20 ` AngeloGioacchino Del Regno
2023-11-16 14:52 ` Bo Ye (叶波) [this message]
2023-12-11 20:52 ` Rafael J. Wysocki
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=81ad0d7dcb82c6f1f49e6d0882249231682c1b6c.camel@mediatek.com \
--to=bo.ye@mediatek.com \
--cc=C.Cheng@mediatek.com \
--cc=Yongdong.Zhang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@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