linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: kbuild-all@lists.01.org,
	Christophe Leroy <christophe.leroy@c-s.fr>, Qian Cai <cai@lca.pw>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 9231/9662] arch/s390/include/asm/pgtable.h:1279:21: sparse: sparse: context imbalance in 'debug_vm_pgtable' - unexpected unlock
Date: Mon, 18 May 2020 21:03:25 +0800	[thread overview]
Message-ID: <202005182116.W6xbY1Oe%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   bdecf38f228bcca73b31ada98b5b7ba1215eb9c9
commit: b707bb13bbeb3348aba518731fa96d3f4ad335ba [9231/9662] mm/debug: add tests validating architecture page table helpers
config: s390-randconfig-s002-20200518 (attached as .config)
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-193-gb8fad4bc-dirty
        git checkout b707bb13bbeb3348aba518731fa96d3f4ad335ba
        # save the attached .config to linux build tree
        make C=1 ARCH=s390 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)

>> arch/s390/include/asm/pgtable.h:1279:21: sparse: sparse: context imbalance in 'debug_vm_pgtable' - unexpected unlock

vim +/debug_vm_pgtable +1279 arch/s390/include/asm/pgtable.h

^1da177e4c3f415 include/asm-s390/pgtable.h      Linus Torvalds     2005-04-16  1278  
190a1d722a59725 include/asm-s390/pgtable.h      Martin Schwidefsky 2007-10-22 @1279  static inline pmd_t *pmd_offset(pud_t *pud, unsigned long address)
^1da177e4c3f415 include/asm-s390/pgtable.h      Linus Torvalds     2005-04-16  1280  {
d1874a0c2805fcf arch/s390/include/asm/pgtable.h Martin Schwidefsky 2019-04-23  1281  	if ((pud_val(*pud) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R3)
d1874a0c2805fcf arch/s390/include/asm/pgtable.h Martin Schwidefsky 2019-04-23  1282  		return (pmd_t *) pud_deref(*pud) + pmd_index(address);
d1874a0c2805fcf arch/s390/include/asm/pgtable.h Martin Schwidefsky 2019-04-23  1283  	return (pmd_t *) pud;
d1874a0c2805fcf arch/s390/include/asm/pgtable.h Martin Schwidefsky 2019-04-23  1284  }
1aea9b3f921003f arch/s390/include/asm/pgtable.h Martin Schwidefsky 2017-04-24  1285  

:::::: The code at line 1279 was first introduced by commit
:::::: 190a1d722a59725706daf832bc8a511ed62f249d [S390] 4level-fixup cleanup

:::::: TO: Martin Schwidefsky <schwidefsky@de.ibm.com>
:::::: CC: Martin Schwidefsky <schwidefsky@de.ibm.com>

---
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: 29187 bytes --]

                 reply	other threads:[~2020-05-18 13:05 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=202005182116.W6xbY1Oe%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=cai@lca.pw \
    --cc=christophe.leroy@c-s.fr \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@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