All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Amit Pundir <amit.pundir@linaro.org>,
	Hugo Benichi <hugobenichi@google.com>,
	Guenter Roeck <groeck@chromium.org>
Subject: [jsarha:topic/cros-sof-v4.14-rebase 2874/9999] net/ipv6/route.c:2623:5: sparse: sparse: symbol 'rt6_addrconf_purge' was not declared. Should it be static?
Date: Fri, 21 Apr 2023 16:28:04 +0800	[thread overview]
Message-ID: <202304211637.MYwfelKT-lkp@intel.com> (raw)

tree:   https://github.com/jsarha/linux topic/cros-sof-v4.14-rebase
head:   18a233f3f676a98dde00947535d99ab1a54da340
commit: ba363662d10c7893123176454fed878d431c895e [2874/9999] ANDROID: net: ipv6: autoconf routes into per-device tables
config: x86_64-randconfig-s022 (https://download.01.org/0day-ci/archive/20230421/202304211637.MYwfelKT-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-39-gce1a6720-dirty
        # https://github.com/jsarha/linux/commit/ba363662d10c7893123176454fed878d431c895e
        git remote add jsarha https://github.com/jsarha/linux
        git fetch --no-tags jsarha topic/cros-sof-v4.14-rebase
        git checkout ba363662d10c7893123176454fed878d431c895e
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 olddefconfig
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash LDFLAGS=-z max-page-size=0x200000  net/ipv6/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304211637.MYwfelKT-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   net/ipv6/route.c:1253:31: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] flow_label @@     got restricted __be32 @@
   net/ipv6/route.c:1253:31: sparse:     expected unsigned int [usertype] flow_label
   net/ipv6/route.c:1253:31: sparse:     got restricted __be32
>> net/ipv6/route.c:2623:5: sparse: sparse: symbol 'rt6_addrconf_purge' was not declared. Should it be static?
   net/ipv6/route.c:2623:5: warning: no previous declaration for 'rt6_addrconf_purge' [-Wmissing-declarations]
    int rt6_addrconf_purge(struct rt6_info *rt, void *arg) {
        ^~~~~~~~~~~~~~~~~~
   arch/x86/include/asm/bitops.h: Assembler messages:
   arch/x86/include/asm/bitops.h:97: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'

vim +/rt6_addrconf_purge +2623 net/ipv6/route.c

  2622	
> 2623	int rt6_addrconf_purge(struct rt6_info *rt, void *arg) {
  2624		if (rt->rt6i_flags & (RTF_DEFAULT | RTF_ADDRCONF) &&
  2625		    (!rt->rt6i_idev || rt->rt6i_idev->cnf.accept_ra != 2))
  2626			return -1;
  2627		return 0;
  2628	}
  2629	

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

                 reply	other threads:[~2023-04-21  8:28 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=202304211637.MYwfelKT-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=amit.pundir@linaro.org \
    --cc=groeck@chromium.org \
    --cc=hugobenichi@google.com \
    --cc=lorenzo@google.com \
    --cc=oe-kbuild-all@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.