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: Sat, 29 Jul 2023 09:19:56 +0800 [thread overview]
Message-ID: <202307290955.JTEbSvfx-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: drivers/net/virtio_net.c:1719:25: sparse: sparse: static assertion failed: "clamp() low limit (unsigned int)(rq->min_buf_len) greater than high limit (unsigned int)((1UL << 13) - hdr_len)""
::::::
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 crng-random/master v6.5-rc3 next-20230728]
[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: 4 days ago
:::::: commit date: 4 days ago
config: openrisc-randconfig-r081-20230728 (https://download.01.org/0day-ci/archive/20230729/202307290955.JTEbSvfx-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230729/202307290955.JTEbSvfx-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/202307290955.JTEbSvfx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/net/virtio_net.c:1719:25: sparse: sparse: bad integer constant expression
>> drivers/net/virtio_net.c:1719:25: sparse: sparse: static assertion failed: "clamp() low limit (unsigned int)(rq->min_buf_len) greater than high limit (unsigned int)((1UL << 13) - hdr_len)"
vim +1719 drivers/net/virtio_net.c
296f96fcfc160e Rusty Russell 2007-10-22 1707
d85b758f72b05a Michael S. Tsirkin 2017-03-09 1708 static unsigned int get_mergeable_buf_len(struct receive_queue *rq,
3cc81a9aac4382 Jason Wang 2018-03-02 1709 struct ewma_pkt_len *avg_pkt_len,
3cc81a9aac4382 Jason Wang 2018-03-02 1710 unsigned int room)
3f2c31d90327f2 Mark McLoughlin 2008-11-16 1711 {
c1ddc42da2b263 Andrew Melnychenko 2022-03-28 1712 struct virtnet_info *vi = rq->vq->vdev->priv;
c1ddc42da2b263 Andrew Melnychenko 2022-03-28 1713 const size_t hdr_len = vi->hdr_len;
fbf28d78f54016 Michael Dalton 2014-01-16 1714 unsigned int len;
fbf28d78f54016 Michael Dalton 2014-01-16 1715
3cc81a9aac4382 Jason Wang 2018-03-02 1716 if (room)
3cc81a9aac4382 Jason Wang 2018-03-02 1717 return PAGE_SIZE - room;
3cc81a9aac4382 Jason Wang 2018-03-02 1718
5377d75823ff90 Johannes Berg 2015-08-19 @1719 len = hdr_len + clamp_t(unsigned int, ewma_pkt_len_read(avg_pkt_len),
f0c3192ceee3c1 Michael S. Tsirkin 2017-06-02 1720 rq->min_buf_len, PAGE_SIZE - hdr_len);
3cc81a9aac4382 Jason Wang 2018-03-02 1721
e377fcc8486d40 Michael S. Tsirkin 2017-03-06 1722 return ALIGN(len, L1_CACHE_BYTES);
fbf28d78f54016 Michael Dalton 2014-01-16 1723 }
fbf28d78f54016 Michael Dalton 2014-01-16 1724
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-07-29 1:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 1:19 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-31 21:23 [PATCH next resend 2/5] minmax: Allow min()/max()/clamp() if the arguments have the same signedness kernel test robot
2023-07-31 20:41 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-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=202307290955.JTEbSvfx-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.