From: David Laight <david.laight.linux@gmail.com>
To: Justin Lai <justinlai0215@realtek.com>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <andrew+netdev@lunn.ch>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<horms@kernel.org>, <pkshih@realtek.com>,
<larry.chiu@realtek.com>
Subject: Re: [PATCH net v2 3/3] rtase: Fix a type error in min_t
Date: Sun, 27 Apr 2025 11:46:46 +0100 [thread overview]
Message-ID: <20250427114646.4253b39d@pumpkin> (raw)
In-Reply-To: <20250416124534.30167-4-justinlai0215@realtek.com>
On Wed, 16 Apr 2025 20:45:34 +0800
Justin Lai <justinlai0215@realtek.com> wrote:
> Fix a type error in min_t.
NAK, in particular u16 is likely to be buggy
Consider what would happen if RTBASE_MITI_MAX_PKT_NUM was 65536.
(Yes, I know that isn't the intent of the code...)
As pointed out earlier using min() shouldn't generate a compile warning
and won't mask off significant bits.
Also I think it isn't a bug in any sense because the two functions
have a single caller that passes a constant.
David
>
> Fixes: a36e9f5cfe9e ("rtase: Add support for a pci table in this module")
> Signed-off-by: Justin Lai <justinlai0215@realtek.com>
> ---
> drivers/net/ethernet/realtek/rtase/rtase_main.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/rtase/rtase_main.c b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> index 55b8d3666153..bc856fb3d6f3 100644
> --- a/drivers/net/ethernet/realtek/rtase/rtase_main.c
> +++ b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> @@ -1923,7 +1923,7 @@ static u16 rtase_calc_time_mitigation(u32 time_us)
> u8 msb, time_count, time_unit;
> u16 int_miti;
>
> - time_us = min_t(int, time_us, RTASE_MITI_MAX_TIME);
> + time_us = min_t(u32, time_us, RTASE_MITI_MAX_TIME);
>
> if (time_us > RTASE_MITI_TIME_COUNT_MASK) {
> msb = fls(time_us);
> @@ -1945,7 +1945,7 @@ static u16 rtase_calc_packet_num_mitigation(u16 pkt_num)
> u8 msb, pkt_num_count, pkt_num_unit;
> u16 int_miti;
>
> - pkt_num = min_t(int, pkt_num, RTASE_MITI_MAX_PKT_NUM);
> + pkt_num = min_t(u16, pkt_num, RTASE_MITI_MAX_PKT_NUM);
>
> if (pkt_num > 60) {
> pkt_num_unit = RTASE_MITI_MAX_PKT_NUM_IDX;
next prev parent reply other threads:[~2025-04-27 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:45 [PATCH net v2 0/3] Fix kernel test robot issue and type error in min_t Justin Lai
2025-04-16 12:45 ` [PATCH net v2 1/3] rtase: Fix the compile error reported by the kernel test robot Justin Lai
2025-04-16 14:16 ` Andrew Lunn
2025-04-17 5:46 ` Justin Lai
2025-04-16 12:45 ` [PATCH net v2 2/3] rtase: Fix the compile warning " Justin Lai
2025-04-16 12:45 ` [PATCH net v2 3/3] rtase: Fix a type error in min_t Justin Lai
2025-04-16 14:17 ` Andrew Lunn
2025-04-27 10:46 ` David Laight [this message]
2025-04-29 8:39 ` Justin Lai
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=20250427114646.4253b39d@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justinlai0215@realtek.com \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).