From: Simon Horman <horms@kernel.org>
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,
pkshih@realtek.com, larry.chiu@realtek.com,
Andrew Lunn <andrew@lunn.ch>,
David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH net v3 3/3] rtase: Fix a type error in min_t
Date: Tue, 22 Apr 2025 14:28:31 +0100 [thread overview]
Message-ID: <20250422132831.GH2843373@horms.kernel.org> (raw)
In-Reply-To: <20250417085659.5740-4-justinlai0215@realtek.com>
+ David Laight
On Thu, Apr 17, 2025 at 04:56:59PM +0800, Justin Lai wrote:
> Fix a type error in min_t.
>
> Fixes: a36e9f5cfe9e ("rtase: Add support for a pci table in this module")
> Signed-off-by: Justin Lai <justinlai0215@realtek.com>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> ---
> 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);
Hi Justin, Andrew, David, all,
I may be on the wrong track here, but near the top of minmax.h I see:
/*
* min()/max()/clamp() macros must accomplish several things:
*
* - Avoid multiple evaluations of the arguments (so side-effects like
* "x++" happen only once) when non-constant.
* - Perform signed v unsigned type-checking (to generate compile
* errors instead of nasty runtime surprises).
* - Unsigned char/short are always promoted to signed int and can be
* compared against signed or unsigned arguments.
* - Unsigned arguments can be compared against non-negative signed constants.
* - Comparison of a signed argument against an unsigned constant fails
* even if the constant is below __INT_MAX__ and could be cast to int.
*/
So, considering the 2nd last point, I think we can simply use min()
both above and below. Which would avoid the possibility of
casting to the wrong type again in future.
Also, aside from which call is correct. Please add some colour
to the commit message describing why this is a bug if it is
to be treated as a fix for net rather than a clean-up for net-next.
>
> 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;
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-04-22 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 8:56 [PATCH net v3 0/3] Modify overflow detection, expand ivec->name, and correct type in min_t Justin Lai
2025-04-17 8:56 ` [PATCH net v3 1/3] rtase: Modify the condition used to detect overflow in rtase_calc_time_mitigation Justin Lai
2025-04-22 13:20 ` Simon Horman
2025-04-23 11:32 ` Justin Lai
2025-04-17 8:56 ` [PATCH net v3 2/3] rtase: Increase the size of ivec->name Justin Lai
2025-04-22 12:55 ` Simon Horman
2025-04-23 11:53 ` Justin Lai
2025-04-23 16:16 ` Simon Horman
2025-04-17 8:56 ` [PATCH net v3 3/3] rtase: Fix a type error in min_t Justin Lai
2025-04-22 13:28 ` Simon Horman [this message]
2025-04-23 10:53 ` Justin Lai
2025-04-23 16:16 ` Simon Horman
2025-04-27 9:57 ` David Laight
2025-04-29 8:46 ` 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=20250422132831.GH2843373@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--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).