From: kernel test robot <lkp@intel.com>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: [linux-stable-rc:linux-5.17.y 1407/3797] net/openvswitch/flow_netlink.o: warning: objtool: ovs_nla_free_nested_actions()+0x56: unreachable instruction
Date: Tue, 14 Jun 2022 18:15:10 +0800 [thread overview]
Message-ID: <202206141802.RwIEdKtZ-lkp@intel.com> (raw)
Hi Ilya,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.17.y
head: a554a1e2ef7fa48cebd9cc2349804974247c0958
commit: 53bce9d19b0a9d245b25cd050b81652ed974a509 [1407/3797] net: openvswitch: fix leak of nested actions
config: x86_64-randconfig-r026-20220613 (https://download.01.org/0day-ci/archive/20220614/202206141802.RwIEdKtZ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=53bce9d19b0a9d245b25cd050b81652ed974a509
git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git fetch --no-tags linux-stable-rc linux-5.17.y
git checkout 53bce9d19b0a9d245b25cd050b81652ed974a509
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/ net/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> net/openvswitch/flow_netlink.o: warning: objtool: ovs_nla_free_nested_actions()+0x56: unreachable instruction
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-14 10:15 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=202206141802.RwIEdKtZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=i.maximets@ovn.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox