public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: david laight <david.laight@runbox.com>
Cc: Frank Li <Frank.li@nxp.com>,
	carlos.song@nxp.com, broonie@kernel.org, rongqianfeng@vivo.com,
	linux-spi@vger.kernel.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: spi-fsl-lpspi: fix watermark truncation caused by type cast
Date: Tue, 25 Nov 2025 16:11:03 +0100	[thread overview]
Message-ID: <aSXHB_CWYZYnQ6ui@black.igk.intel.com> (raw)
In-Reply-To: <20251122105716.24769251@pumpkin>

On Sat, Nov 22, 2025 at 10:57:16AM +0000, david laight wrote:
> On Fri, 21 Nov 2025 11:19:34 -0500
> Frank Li <Frank.li@nxp.com> wrote:
> > On Mon, Nov 17, 2025 at 11:03:55AM +0800, carlos.song@nxp.com wrote:

...

> > > +	/*
> > > +	 * t->len is 'unsigned' and txfifosize and watermrk is 'u8', force
> > > +	 * type cast is inevitable. When len > 255, len will be truncated in min_t(),
> > > +	 * it caused wrong watermark set. 'unsigned int' is as the designated type
> > > +	 * for min_t() to avoid truncation.
> > > +	 */
> > > +	fsl_lpspi->watermark = min_t(unsigned int,
> > >  				     fsl_lpspi->txfifosize,
> > >  				     t->len);  
> > 
> > There are thread discussion about min() and min_t()
> > 
> > https://lore.kernel.org/all/20251119224140.8616-1-david.laight.linux@gmail.com/
> 
> The big comment even carefully explains that the two types are unsigned ones.
> So a simple min() is absolutely fine (and the comment can go away).
> 
> The old typecheck in min was just so stupid.
> In this case the 'u8' variable is promoted to 'int' (they always are)
> and then converted to 'unsigned int' to match the other type.
> Even though there is an implicit 'int' => 'unsigned int' cast it is
> impossible for a negative value to become a large positive on
> (which is the only justification for the type check).
> 
> I'd check the file for other uses on min_t() as well.

Just came to this thread to echoing what David said. +1 to the above, please
convert to simple min(). The use cases for min_t() and max_t() should be rare
really.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-11-25 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  3:03 [PATCH] spi: spi-fsl-lpspi: fix watermark truncation caused by type cast carlos.song
2025-11-21  8:18 ` Carlos Song
2025-11-21 14:23   ` Mark Brown
2025-11-21  9:30 ` Daniel Baluta
2025-11-21 15:54 ` Frank Li
2025-11-21 16:19 ` Frank Li
2025-11-22 10:57   ` david laight
2025-11-25 15:11     ` Andy Shevchenko [this message]
2025-11-26  2:10       ` Carlos Song
2025-11-26  6:43         ` Andy Shevchenko
2025-11-26 10:02           ` Carlos Song
2025-11-21 16:24 ` Mark Brown
2025-11-22 10:48 ` david laight

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=aSXHB_CWYZYnQ6ui@black.igk.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Frank.li@nxp.com \
    --cc=broonie@kernel.org \
    --cc=carlos.song@nxp.com \
    --cc=david.laight@runbox.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=rongqianfeng@vivo.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