From: kernel test robot <lkp@intel.com>
To: Paul Blakey <paulb@nvidia.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Oz Shlomo <ozsh@nvidia.com>
Subject: [saeed:net-next 612/668] net/openvswitch/flow.c:915:19: warning: variable 'zone' is uninitialized when used here
Date: Wed, 1 Dec 2021 09:24:22 +0800 [thread overview]
Message-ID: <202112010929.w3wcdBWp-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git net-next
head: 960dff4cc0bfc59cc7a168c8f1e1f58c93f6a10d
commit: dff3da2f663fdac40a3d72b85ee3b5f89e88501f [612/668] net: openvswitch: Fix matching zone id for invalid conns arriving from tc
config: x86_64-randconfig-r022-20211130 (https://download.01.org/0day-ci/archive/20211201/202112010929.w3wcdBWp-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 25eb7fa01d7ebbe67648ea03841cda55b4239ab2)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/commit/?id=dff3da2f663fdac40a3d72b85ee3b5f89e88501f
git remote add saeed https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
git fetch --no-tags saeed net-next
git checkout dff3da2f663fdac40a3d72b85ee3b5f89e88501f
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash net/openvswitch/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> net/openvswitch/flow.c:915:19: warning: variable 'zone' is uninitialized when used here [-Wuninitialized]
key->ct_zone = zone;
^~~~
net/openvswitch/flow.c:864:10: note: initialize the variable 'zone' to silence this warning
u16 zone;
^
= 0
1 warning generated.
vim +/zone +915 net/openvswitch/flow.c
910
911 err = key_extract(skb, key);
912 if (!err) {
913 ovs_ct_fill_key(skb, key, post_ct); /* Must be after key_extract(). */
914 if (post_ct && !skb_get_nfct(skb))
> 915 key->ct_zone = zone;
916 }
917 return err;
918 }
919
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-01 1:25 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=202112010929.w3wcdBWp-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.com \
--cc=saeedm@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox