From: Dan Carpenter <dan.carpenter@linaro.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Yangbo Lu <yangbo.lu@nxp.com>,
Richard Cochran <richardcochran@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net] ptp: fix integer overflow in max_vclocks_store
Date: Mon, 17 Jun 2024 09:01:57 +0300 [thread overview]
Message-ID: <591ae05a-7ad4-4ff7-943d-d8ecc17c91ca@moroto.mountain> (raw)
In-Reply-To: <3946b327-5e89-43d3-9dc3-10dd10bd41bc@wanadoo.fr>
On Sat, Jun 15, 2024 at 09:05:56AM +0200, Christophe JAILLET wrote:
> Le 14/06/2024 à 19:31, Dan Carpenter a écrit :
> > On 32bit systems, the "4 * max" multiply can overflow. Use size_mul()
> > to fix this.
> >
> > Fixes: 44c494c8e30e ("ptp: track available ptp vclocks information")
> > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> > ---
> > drivers/ptp/ptp_sysfs.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/ptp/ptp_sysfs.c b/drivers/ptp/ptp_sysfs.c
> > index a15460aaa03b..bc1562fcd6c9 100644
> > --- a/drivers/ptp/ptp_sysfs.c
> > +++ b/drivers/ptp/ptp_sysfs.c
> > @@ -296,7 +296,7 @@ static ssize_t max_vclocks_store(struct device *dev,
> > if (max < ptp->n_vclocks)
> > goto out;
> > - size = sizeof(int) * max;
> > + size = size_mul(sizeof(int), max);
> > vclock_index = kzalloc(size, GFP_KERNEL);
>
> kcalloc() maybe?
>
Fair enough. I'll resend.
> > if (!vclock_index) {
> > err = -ENOMEM;
>
>
> Unrelated but, a few lines above, should the:
> if (max == ptp->max_vclocks)
> return count;
>
> be after:
> if (mutex_lock_interruptible(&ptp->n_vclocks_mux))
> return -ERESTARTSYS;
>
> as done in n_vclocks_store()?
The code is probably better as is. This is a short cut path. We
sometimes see this pattern on fast paths where we test to see if we can
skip everything, then we test again underlock if the test is really
essential. Here if max == ptp->max_vclocks then the whole function is
very complicated no-op so it's not necessary to retest under the lock.
Meanwhile the essential "if (max < ptp->n_vclocks)" check is done under
lock. So it works and it feels like someone put some thought into it.
regards,
dan carpenter
prev parent reply other threads:[~2024-06-17 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 17:31 [PATCH net] ptp: fix integer overflow in max_vclocks_store Dan Carpenter
2024-06-15 7:05 ` Christophe JAILLET
2024-06-17 6:01 ` Dan Carpenter [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=591ae05a-7ad4-4ff7-943d-d8ecc17c91ca@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=yangbo.lu@nxp.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