From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [block:for-5.5/io_uring-wq 14/14] include/linux/spinlock.h:378:9: sparse: sparse: context imbalance in 'io_wqe_worker' - unexpected unlock
Date: Fri, 25 Oct 2019 16:10:21 +0800 [thread overview]
Message-ID: <201910251616.MHr4FN9B%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-5.5/io_uring-wq
head: 25fba7014fd1e953222bba0dad26694c9b2646c1
commit: 25fba7014fd1e953222bba0dad26694c9b2646c1 [14/14] io_uring: replace workqueue with io-wq
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-dirty
git checkout 25fba7014fd1e953222bba0dad26694c9b2646c1
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
fs/io-wq.c:186:13: sparse: sparse: context imbalance in '__io_worker_idle' - different lock contexts for basic block
>> include/linux/spinlock.h:378:9: sparse: sparse: context imbalance in 'io_wqe_worker' - unexpected unlock
vim +/io_wqe_worker +378 include/linux/spinlock.h
c2f21ce2e31286 Thomas Gleixner 2009-12-02 375
3490565b633c70 Denys Vlasenko 2015-07-13 376 static __always_inline void spin_unlock(spinlock_t *lock)
c2f21ce2e31286 Thomas Gleixner 2009-12-02 377 {
c2f21ce2e31286 Thomas Gleixner 2009-12-02 @378 raw_spin_unlock(&lock->rlock);
c2f21ce2e31286 Thomas Gleixner 2009-12-02 379 }
c2f21ce2e31286 Thomas Gleixner 2009-12-02 380
:::::: The code at line 378 was first introduced by commit
:::::: c2f21ce2e31286a0a32f8da0a7856e9ca1122ef3 locking: Implement new raw_spinlock
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
reply other threads:[~2019-10-25 8:10 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=201910251616.MHr4FN9B%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.