public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: William Hansen-Baird <william.hansen.baird@gmail.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	gregkh@linuxfoundation.org, straube.linux@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: replace ternary comparison with min_t()
Date: Sat, 31 Jan 2026 22:58:41 +0000	[thread overview]
Message-ID: <20260131225841.6ec19c9d@pumpkin> (raw)
In-Reply-To: <aX53mt0cFlcz_2VB@william-fedora>

On Sat, 31 Jan 2026 16:43:54 -0500
William Hansen-Baird <william.hansen.baird@gmail.com> wrote:

> On Sat, Jan 31, 2026 at 08:35:55PM +0300, Dan Carpenter wrote:
> > On Sat, Jan 31, 2026 at 03:55:25PM +0000, David Laight wrote:  
> > > > > @@ -1024,7 +1025,7 @@ static unsigned short rtw_parse_assoc_security_ies(struct adapter *padapter,
> > > > >  			pstat->flags |= WLAN_STA_WPS;
> > > > >  			copy_len = 0;
> > > > >  		} else {
> > > > > -			copy_len = ((wpa_ie_len+2) > sizeof(pstat->wpa_ie)) ? (sizeof(pstat->wpa_ie)):(wpa_ie_len+2);
> > > > > +			copy_len = min_t(int, sizeof(pstat->wpa_ie), wpa_ie_len + 2);    
> > > > 
> > > > Use umin().  "int" is wrong because we don't want negative values
> > > > stored in copy_len.  
> > > 
> > > And the correct way to fix min() bleating is to change the type of the variables.
> > > Using min_t() ought to be frowned up and only used as a last resort.
> > > 
> > > In this case I think all the variables declared with wpa_ie_len can/should be
> > > unsigned int.
> > >   
> > 
> > That also works.
> >   
> Hi Dan and David,
> 
> Thanks for your help. After reviewing the code, I do see a few checks 
> ensuring wpa_ie_len is never negative.
> Therefore umin() is safe in this case, and for v3 I'll update the patch accordingly.

umin() is a bit better than min_t().

A subtle change is doing 'wpa_ie_len + 2u'.

> Would you prefer I leave it at that, or is a broader change to 
> make wpa_ie_len unsigned worth doing in a separate patch?

I scanned the code some of the variables seem to be different signedness 
in different functions.

But a 'false error' from min() is really an indication you should be looking
at changing the types of the variables themselves.

My main thought looking at that code is that functions are far too long
and have far too many local variables.
You also pretty much don't want to use u8/u16 for locals just because the
values are small, it doesn't (really) save space and can increase code size.

	David

> 
> Thanks,
> William


      reply	other threads:[~2026-01-31 22:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 13:31 [PATCH v2] staging: rtl8723bs: replace ternary comparison with min_t() William Hansen-Baird
2026-01-31 14:43 ` Dan Carpenter
2026-01-31 15:55   ` David Laight
2026-01-31 17:35     ` Dan Carpenter
2026-01-31 21:43       ` William Hansen-Baird
2026-01-31 22:58         ` David Laight [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=20260131225841.6ec19c9d@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=straube.linux@gmail.com \
    --cc=william.hansen.baird@gmail.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