From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [jirislaby:devel 77/98] drivers/block/xen-blkfront.c:280:9: sparse: sparse: too long token expansion
Date: Tue, 16 Feb 2021 00:46:59 +0800 [thread overview]
Message-ID: <202102160055.LTco4DMA-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]
CC: kbuild-all(a)lists.01.org
TO: Jiri Slaby <jslaby@suse.cz>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git devel
head: 1494092ef6d50f60cf63d298959874e1f653e4a1
commit: d0b9e71824ebadc9e9516b7a5cfa028068011fed [77/98] include condition in the BUG_ON/WARN_ON output
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: x86_64-randconfig-s021-20210215 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-215-g0fb77bb6-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/commit/?id=d0b9e71824ebadc9e9516b7a5cfa028068011fed
git remote add jirislaby https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git
git fetch --no-tags jirislaby devel
git checkout d0b9e71824ebadc9e9516b7a5cfa028068011fed
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> drivers/block/xen-blkfront.c:280:9: sparse: sparse: too long token expansion
vim +280 drivers/block/xen-blkfront.c
4ab50af63d2eb5 Juergen Gross 2020-03-05 275
81f35161577236 Bob Liu 2015-11-14 276 static int get_id_from_freelist(struct blkfront_ring_info *rinfo)
9f27ee59503865 Jeremy Fitzhardinge 2007-07-17 277 {
81f35161577236 Bob Liu 2015-11-14 278 unsigned long free = rinfo->shadow_free;
81f35161577236 Bob Liu 2015-11-14 279
81f35161577236 Bob Liu 2015-11-14 @280 BUG_ON(free >= BLK_RING_SIZE(rinfo->dev_info));
81f35161577236 Bob Liu 2015-11-14 281 rinfo->shadow_free = rinfo->shadow[free].req.u.rw.id;
81f35161577236 Bob Liu 2015-11-14 282 rinfo->shadow[free].req.u.rw.id = 0x0fffffee; /* debug */
9f27ee59503865 Jeremy Fitzhardinge 2007-07-17 283 return free;
9f27ee59503865 Jeremy Fitzhardinge 2007-07-17 284 }
9f27ee59503865 Jeremy Fitzhardinge 2007-07-17 285
:::::: The code at line 280 was first introduced by commit
:::::: 81f351615772365d46ceeac3e50c9dd4e8f9dc89 xen/blkfront: separate per ring information out of device info
:::::: TO: Bob Liu <bob.liu@oracle.com>
:::::: CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 30512 bytes --]
reply other threads:[~2021-02-15 16:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202102160055.LTco4DMA-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.org \
/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.