| 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
| ||
|
Date: Fri, 23 Jan 2015 20:12:06 +0800 From: kbuild test robot <fengguang.wu@...el.com> To: Thomas Gleixner <tglx@...utronix.de> Cc: kbuild-all@...org, linux-kernel@...r.kernel.org Subject: [tip:timers/core 2/2] kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static? tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core head: 9bc7491906b4113b4c5ae442157c7dfc4e10cd14 commit: 9bc7491906b4113b4c5ae442157c7dfc4e10cd14 [2/2] hrtimer: Prevent stale expiry time in hrtimer_interrupt() reproduce: # apt-get install sparse git checkout 9bc7491906b4113b4c5ae442157c7dfc4e10cd14 make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) kernel/time/hrtimer.c:67:1: sparse: symbol '__pcpu_scope_hrtimer_bases' was not declared. Should it be static? >> kernel/time/hrtimer.c:444:9: sparse: symbol '__hrtimer_get_next_event' was not declared. Should it be static? kernel/time/hrtimer.c:152:27: sparse: context imbalance in 'lock_hrtimer_base' - wrong count at exit kernel/time/hrtimer.c:994:25: sparse: context imbalance in '__hrtimer_start_range_ns' - unexpected unlock kernel/time/hrtimer.c:793:9: sparse: context imbalance in 'hrtimer_try_to_cancel' - unexpected unlock kernel/time/hrtimer.c:1099:9: sparse: context imbalance in 'hrtimer_get_remaining' - unexpected unlock 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/
Powered by blists - more mailing lists