All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH next resend 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness.
Date: Tue, 1 Aug 2023 05:23:21 +0800	[thread overview]
Message-ID: <202308010503.8XSvuAs8-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check first_new_problem: drivers/net/usb/cdc_ncm.c:166:15: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <a09512c8526b46759669d0b879144563@AcuMS.aculab.com>
References: <a09512c8526b46759669d0b879144563@AcuMS.aculab.com>
TO: David Laight <David.Laight@ACULAB.COM>
TO: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
TO: "'Andy Shevchenko'" <andriy.shevchenko@linux.intel.com>
TO: "'Andrew Morton'" <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: "'Matthew Wilcox (Oracle)'" <willy@infradead.org>
TO: "'Christoph Hellwig'" <hch@infradead.org>
TO: "'Jason A. Donenfeld'" <Jason@zx2c4.com>

Hi David,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on linus/master v6.5-rc4 next-20230731]
[cannot apply to next-20230725]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/David-Laight/minmax-Allow-min-max-clamp-if-the-arguments-have-the-same-signedness/20230725-204940
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/a09512c8526b46759669d0b879144563%40AcuMS.aculab.com
patch subject: [PATCH next resend 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness.
:::::: branch date: 6 days ago
:::::: commit date: 6 days ago
config: i386-randconfig-i061-20230730 (https://download.01.org/0day-ci/archive/20230801/202308010503.8XSvuAs8-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230801/202308010503.8XSvuAs8-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202308010503.8XSvuAs8-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/net/usb/cdc_ncm.c:166:15: sparse: sparse: bad integer constant expression
>> drivers/net/usb/cdc_ncm.c:166:15: sparse: sparse: static assertion failed: "clamp() low limit (u32)(min) greater than high limit (u32)(max)"
   drivers/net/usb/cdc_ncm.c:194:15: sparse: sparse: bad integer constant expression
   drivers/net/usb/cdc_ncm.c:194:15: sparse: sparse: static assertion failed: "clamp() low limit (u32)(min) greater than high limit (u32)(max)"
   drivers/net/usb/cdc_ncm.c:472:27: sparse: sparse: bad integer constant expression
>> drivers/net/usb/cdc_ncm.c:472:27: sparse: sparse: static assertion failed: "clamp() low limit (u16)(512) greater than high limit (u16)(ctx->tx_max)"
   drivers/net/usb/cdc_ncm.c:618:34: sparse: sparse: bad integer constant expression
>> drivers/net/usb/cdc_ncm.c:618:34: sparse: sparse: static assertion failed: "clamp() low limit (u32)(cdc_ncm_min_dgram_size(dev)) greater than high limit (u32)(8192)"
--
>> drivers/media/platform/xilinx/xilinx-dma.c:548:22: sparse: sparse: bad integer constant expression
>> drivers/media/platform/xilinx/xilinx-dma.c:548:22: sparse: sparse: static assertion failed: "clamp() low limit min_width greater than high limit max_width"
   drivers/media/platform/xilinx/xilinx-dma.c:560:29: sparse: sparse: bad integer constant expression
>> drivers/media/platform/xilinx/xilinx-dma.c:560:29: sparse: sparse: static assertion failed: "clamp() low limit min_bpl greater than high limit max_bpl"

vim +166 drivers/net/usb/cdc_ncm.c

6c4e548ff36672 Bjørn Mork 2014-05-16  149  
289507d3364f96 Bjørn Mork 2014-05-30  150  static u32 cdc_ncm_check_rx_max(struct usbnet *dev, u32 new_rx)
5aa73d5d72bddf Bjørn Mork 2014-05-16  151  {
5aa73d5d72bddf Bjørn Mork 2014-05-16  152  	struct cdc_ncm_ctx *ctx = (struct cdc_ncm_ctx *)dev->data[0];
5aa73d5d72bddf Bjørn Mork 2014-05-16  153  	u32 val, max, min;
5aa73d5d72bddf Bjørn Mork 2014-05-16  154  
5aa73d5d72bddf Bjørn Mork 2014-05-16  155  	/* clamp new_rx to sane values */
5aa73d5d72bddf Bjørn Mork 2014-05-16  156  	min = USB_CDC_NCM_NTB_MIN_IN_SIZE;
5aa73d5d72bddf Bjørn Mork 2014-05-16  157  	max = min_t(u32, CDC_NCM_NTB_MAX_SIZE_RX, le32_to_cpu(ctx->ncm_parm.dwNtbInMaxSize));
5aa73d5d72bddf Bjørn Mork 2014-05-16  158  
5aa73d5d72bddf Bjørn Mork 2014-05-16  159  	/* dwNtbInMaxSize spec violation? Use MIN size for both limits */
5aa73d5d72bddf Bjørn Mork 2014-05-16  160  	if (max < min) {
5aa73d5d72bddf Bjørn Mork 2014-05-16  161  		dev_warn(&dev->intf->dev, "dwNtbInMaxSize=%u is too small. Using %u\n",
5aa73d5d72bddf Bjørn Mork 2014-05-16  162  			 le32_to_cpu(ctx->ncm_parm.dwNtbInMaxSize), min);
5aa73d5d72bddf Bjørn Mork 2014-05-16  163  		max = min;
5aa73d5d72bddf Bjørn Mork 2014-05-16  164  	}
5aa73d5d72bddf Bjørn Mork 2014-05-16  165  
5aa73d5d72bddf Bjørn Mork 2014-05-16 @166  	val = clamp_t(u32, new_rx, min, max);
289507d3364f96 Bjørn Mork 2014-05-30  167  	if (val != new_rx)
289507d3364f96 Bjørn Mork 2014-05-30  168  		dev_dbg(&dev->intf->dev, "rx_max must be in the [%u, %u] range\n", min, max);
289507d3364f96 Bjørn Mork 2014-05-30  169  
289507d3364f96 Bjørn Mork 2014-05-30  170  	return val;
289507d3364f96 Bjørn Mork 2014-05-30  171  }
289507d3364f96 Bjørn Mork 2014-05-30  172  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2023-07-31 21:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 21:23 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-31 20:41 [PATCH next resend 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness kernel test robot
2023-07-31 20:20 kernel test robot
2023-07-30  1:38 kernel test robot
2023-07-30  1:08 kernel test robot
2023-07-29  3:54 kernel test robot
2023-07-29  2:41 kernel test robot
2023-07-29  2:00 kernel test robot
2023-07-29  1:19 kernel test robot
2023-07-28 23:47 kernel test robot
2023-07-28 10:25 kernel test robot
2023-07-28  9:53 kernel test robot
2023-07-27 21:24 kernel test robot
2023-07-27 12:37 kernel test robot
2023-07-27  3:27 kernel test robot
2023-07-26 23:47 kernel test robot
2023-07-26 21:10 kernel test robot
2023-07-26 19:58 kernel test robot
2023-07-26 12:15 kernel test robot
2023-07-26  9:50 kernel test robot
2023-07-26  9:39 kernel test robot
2023-07-26  9:29 kernel test robot
2023-07-26  8:47 kernel test robot
2023-07-26  8:36 kernel test robot
2023-07-26  8:05 kernel test robot
2023-07-25 10:00 [PATCH next 0/5] minmax: Relax type checks in min() and max() David Laight
2023-07-25 11:51 ` [PATCH next resend 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness David Laight
2023-07-25 18:02   ` kernel test robot
2023-07-25 18:33   ` kernel test robot
2023-07-26  9:19     ` David Laight
2023-07-26  9:50       ` Marc Zyngier
2023-07-26 10:25         ` 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=202308010503.8XSvuAs8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.