From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Guangbin Huang <huangguangbin2@huawei.com>,
Andrew Lunn <andrew@lunn.ch>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
Tom Rix <trix@redhat.com>, Marco Bonelli <marco@mebeim.net>,
Edward Cree <ecree@solarflare.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH v3] ethtool: avoiding integer overflow in ethtool_phys_id()
Date: Tue, 22 Nov 2022 14:39:08 +0100 [thread overview]
Message-ID: <20221122133908.422677-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <20221122122901.22294-1-korotkov.maxim.s@gmail.com>
From: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Date: Tue, 22 Nov 2022 15:29:01 +0300
> The value of an arithmetic expression "n * id.data" is subject
> to possible overflow due to a failure to cast operands to a larger data
> type before performing arithmetic. Used macro for multiplication instead
> operator for avoiding overflow.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Reviewed-by: Alexander Lobakin <alexandr.lobakin@intel.com>
> ---
> net/ethtool/ioctl.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/ethtool/ioctl.c b/net/ethtool/ioctl.c
> index 6a7308de192d..6b59e7a1c906 100644
> --- a/net/ethtool/ioctl.c
> +++ b/net/ethtool/ioctl.c
> @@ -2007,7 +2007,8 @@ static int ethtool_phys_id(struct net_device *dev, void __user *useraddr)
> } else {
> /* Driver expects to be called at twice the frequency in rc */
> int n = rc * 2, interval = HZ / n;
> - u64 count = n * id.data, i = 0;
> + u64 count = mul_u32_u32(n, id.data);
> + u64 i = 0;
>
> do {
> rtnl_lock();
> --
> 2.17.1
Some notes to the process, not the code:
1) I asked to add my Reviewed-by to v3 in the previous thread, it's
mandatory for authors to pick-up all the tags before publishing
a new revision;
2) when sending v2, v3, ... vN, please have a changelog in the
commit message or right below those '---' after your SoB, that
makes it easier to review.
Thanks,
Olek
next prev parent reply other threads:[~2022-11-22 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:29 Maxim Korotkov
2022-11-22 13:39 ` Alexander Lobakin [this message]
2022-11-22 14:49 ` Andrew Lunn
2022-11-24 4:11 ` Jakub Kicinski
2022-11-24 4:20 ` patchwork-bot+netdevbpf
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=20221122133908.422677-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=edumazet@google.com \
--cc=huangguangbin2@huawei.com \
--cc=jacob.e.keller@intel.com \
--cc=korotkov.maxim.s@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=marco@mebeim.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=trix@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®