Oh boy, there's more of the trace which appears much further down in
dmesg and the printk timestamps are all messed up!?! See below.
On Tue, Feb 25, 2014 at 12:17:48AM +0100, Borislav Petkov wrote:
From: Kyle McMartin <redacted>
Boris reports he's seeing:
[ 9.195943] INFO: trying to register non-static key.
[ 9.196031] the code is fine but needs lockdep annotation.
[ 9.196031] turning off the locking correctness validator.
[ 9.196031] CPU: 1 PID: 933 Comm: modprobe Not tainted 3.14.0-rc4+ #1
with the r8169 driver.
These are occuring because the seqcount embedded in u64_stats_sync on
32-bit SMP is uninitialized which is making lockdep unhappy.
Signed-off-by: Kyle McMartin <redacted>
---
Patch is only compile tested by me, as these initializers will disappear
on 64-bit.
From: Kyle McMartin <redacted>
Boris reports he's seeing:
quoted
[ 9.195943] INFO: trying to register non-static key.
[ 9.196031] the code is fine but needs lockdep annotation.
[ 9.196031] turning off the locking correctness validator.
[ 9.196031] CPU: 1 PID: 933 Comm: modprobe Not tainted 3.14.0-rc4+ #1
with the r8169 driver.
These are occuring because the seqcount embedded in u64_stats_sync on
32-bit SMP is uninitialized which is making lockdep unhappy.
Signed-off-by: Kyle McMartin <redacted>
On Mon, Feb 24, 2014 at 08:32:40PM -0500, David Miller wrote:
quoted
Boris reports he's seeing:
quoted
[ 9.195943] INFO: trying to register non-static key.
[ 9.196031] the code is fine but needs lockdep annotation.
[ 9.196031] turning off the locking correctness validator.
[ 9.196031] CPU: 1 PID: 933 Comm: modprobe Not tainted 3.14.0-rc4+ #1
with the r8169 driver.
These are occuring because the seqcount embedded in u64_stats_sync on
32-bit SMP is uninitialized which is making lockdep unhappy.
Signed-off-by: Kyle McMartin <redacted>
Good catch, applied, thanks Kyle.
Thanks Kyle!
Tested-by: Borislav Petkov <redacted>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--