From: kernel test robot <lkp@intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Matthieu Baerts <matthieu.baerts@tessares.net>
Subject: arch/x86/include/asm/paravirt.h:650:9: sparse: sparse: context imbalance in 'mptcp_sk_clone' - unexpected unlock
Date: Tue, 9 Jun 2020 01:25:02 +0800 [thread overview]
Message-ID: <202006090154.zJM4f0hL%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: af7b4801030c07637840191c69eb666917e4135d
commit: 58b09919626bf9067345289212ec030c61eb1034 mptcp: create msk early
date: 3 months ago
config: x86_64-randconfig-s022-20200608 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-247-gcadbd124-dirty
git checkout 58b09919626bf9067345289212ec030c61eb1034
# save the attached .config to linux build tree
make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
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 >>)
>> arch/x86/include/asm/paravirt.h:650:9: sparse: sparse: context imbalance in 'mptcp_sk_clone' - unexpected unlock
vim +/mptcp_sk_clone +650 arch/x86/include/asm/paravirt.h
f233f7f1581e78 Peter Zijlstra (Intel 2015-04-24 647)
f233f7f1581e78 Peter Zijlstra (Intel 2015-04-24 648) static __always_inline void pv_queued_spin_unlock(struct qspinlock *lock)
f233f7f1581e78 Peter Zijlstra (Intel 2015-04-24 649) {
5c83511bdb9832 Juergen Gross 2018-08-28 @650 PVOP_VCALLEE1(lock.queued_spin_unlock, lock);
f233f7f1581e78 Peter Zijlstra (Intel 2015-04-24 651) }
f233f7f1581e78 Peter Zijlstra (Intel 2015-04-24 652)
:::::: The code at line 650 was first introduced by commit
:::::: 5c83511bdb9832c86be20fb86b783356e2f58062 x86/paravirt: Use a single ops structure
:::::: TO: Juergen Gross <jgross@suse.com>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33253 bytes --]
reply other threads:[~2020-06-09 0:16 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=202006090154.zJM4f0hL%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®