From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v3 5/5] minmax: Relax check to allow comparison between int and small unsigned constants.
Date: Sat, 5 Aug 2023 07:11:46 +0800 [thread overview]
Message-ID: <202308050640.uLl9ePSK-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: net/ceph/messenger.c:790:9: sparse: sparse: too long token expansion"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <b6a49ed73aba427ca8bb433763fa94e9@AcuMS.aculab.com>
References: <b6a49ed73aba427ca8bb433763fa94e9@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>
TO: "'Linus Torvalds'" <torvalds@linux-foundation.org>
Hi David,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.5-rc4 next-20230804]
[cannot apply to next-20230804 akpm-mm/mm-everything]
[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-Add-min_unsigned-a-b-and-max_unsigned-a-b/20230804-190414
base: linus/master
patch link: https://lore.kernel.org/r/b6a49ed73aba427ca8bb433763fa94e9%40AcuMS.aculab.com
patch subject: [PATCH v3 5/5] minmax: Relax check to allow comparison between int and small unsigned constants.
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: um-randconfig-r091-20230730 (https://download.01.org/0day-ci/archive/20230805/202308050640.uLl9ePSK-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230805/202308050640.uLl9ePSK-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/202308050640.uLl9ePSK-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/ceph/messenger.c:790:9: sparse: sparse: too long token expansion
>> net/ceph/messenger.c:790:9: sparse: sparse: too long token expansion
net/ceph/messenger.c:797:29: sparse: sparse: too long token expansion
net/ceph/messenger.c:797:29: sparse: sparse: too long token expansion
net/ceph/messenger.c:812:9: sparse: sparse: too long token expansion
net/ceph/messenger.c:812:9: sparse: sparse: too long token expansion
net/ceph/messenger.c:823:9: sparse: sparse: too long token expansion
net/ceph/messenger.c:823:9: sparse: sparse: too long token expansion
--
>> net/ipv6/proc.c:186:28: sparse: sparse: too long token expansion
net/ipv6/proc.c:190:57: sparse: sparse: too long token expansion
net/ipv6/proc.c:206:20: sparse: sparse: too long token expansion
net/ipv6/proc.c:209:41: sparse: sparse: too long token expansion
vim +790 net/ceph/messenger.c
df6ad1f97342eb Alex Elder 2012-06-11 779
b9e281c2b38804 Ilya Dryomov 2018-01-20 780 static void ceph_msg_data_bvecs_cursor_init(struct ceph_msg_data_cursor *cursor,
b9e281c2b38804 Ilya Dryomov 2018-01-20 781 size_t length)
b9e281c2b38804 Ilya Dryomov 2018-01-20 782 {
b9e281c2b38804 Ilya Dryomov 2018-01-20 783 struct ceph_msg_data *data = cursor->data;
b9e281c2b38804 Ilya Dryomov 2018-01-20 784 struct bio_vec *bvecs = data->bvec_pos.bvecs;
b9e281c2b38804 Ilya Dryomov 2018-01-20 785
b9e281c2b38804 Ilya Dryomov 2018-01-20 786 cursor->resid = min_t(size_t, length, data->bvec_pos.iter.bi_size);
b9e281c2b38804 Ilya Dryomov 2018-01-20 787 cursor->bvec_iter = data->bvec_pos.iter;
b9e281c2b38804 Ilya Dryomov 2018-01-20 788 cursor->bvec_iter.bi_size = cursor->resid;
b9e281c2b38804 Ilya Dryomov 2018-01-20 789
b9e281c2b38804 Ilya Dryomov 2018-01-20 @790 BUG_ON(cursor->resid < bvec_iter_len(bvecs, cursor->bvec_iter));
b9e281c2b38804 Ilya Dryomov 2018-01-20 791 }
b9e281c2b38804 Ilya Dryomov 2018-01-20 792
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-04 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 23:11 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 4:55 [PATCH v3 5/5] minmax: Relax check to allow comparison between int and small unsigned constants kernel test robot
2023-08-05 6:13 kernel test robot
2023-08-04 23:42 kernel test robot
2023-08-04 23:42 kernel test robot
2023-08-04 23:32 kernel test robot
2023-08-04 23:32 kernel test robot
2023-08-04 22:40 kernel test robot
2023-08-04 21:49 kernel test robot
2023-08-04 21:48 kernel test robot
2023-08-04 10:50 [PATCH next v3 0/5] minmax: Relax type checks in min() and max() David Laight
2023-08-04 10:56 ` [PATCH v3 5/5] minmax: Relax check to allow comparison between int and small unsigned constants David Laight
2023-08-04 18:14 ` Linus Torvalds
2023-08-07 10:50 ` David Laight
2023-08-07 15:48 ` Linus Torvalds
2023-08-10 8:29 ` David Laight
2023-08-10 19:46 ` Linus Torvalds
2023-08-14 8:04 ` David Laight
2023-08-14 14:51 ` David Laight
2023-08-14 15:29 ` 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=202308050640.uLl9ePSK-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.