linux-kernel - [aa:userfault 17/19] mm/userfaultfd.c:48:6: sparse: symbol 'double_down_read' was not declared. Should it be static?

Open Source and information security mailing list archives

Message-ID: <201502121644.mekdzvbV%fengguang.wu@intel.com>
Date:	Thu, 12 Feb 2015 16:54:04 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Andrea Arcangeli <aarcange@...hat.com>
Cc:	kbuild-all@...org, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: [aa:userfault 17/19] mm/userfaultfd.c:48:6: sparse: symbol
 'double_down_read' was not declared. Should it be static?

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git userfault
head:   9866337e3999d167b77303ad9e57fd20919893e3
commit: e2ccdb8c9f49438f9c8910f2f93c7e5ee35d8644 [17/19] userfaultfd: add new syscall to provide memory externalization
reproduce:
  # apt-get install sparse
  git checkout e2ccdb8c9f49438f9c8910f2f93c7e5ee35d8644
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__

sparse warnings: (new ones prefixed by >>)

>> mm/userfaultfd.c:48:6: sparse: symbol 'double_down_read' was not declared. Should it be static?
>> mm/userfaultfd.c:67:6: sparse: symbol 'double_up_read' was not declared. Should it be static?
>> mm/userfaultfd.c:34:9: sparse: context imbalance in 'double_pt_lock' - different lock contexts for basic block
>> mm/userfaultfd.c:44:9: sparse: context imbalance in 'double_pt_unlock' - different lock contexts for basic block
>> mm/userfaultfd.c:63:9: sparse: context imbalance in 'double_down_read' - wrong count at exit
>> mm/userfaultfd.c:73:9: sparse: context imbalance in 'double_up_read' - wrong count at exit
>> mm/userfaultfd.c:551:9: sparse: context imbalance in 'remap_anon_pages' - different lock contexts for basic block

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives