rcu_dereference_check errors from 3.0 kernel

[Genes MailLists]

I'm still seeing these kinds of rcu_dereference_check() messages from
kernel 3.0-0.rc5.git0.1.fc16.x86_64

Same problem on rc3 git5.

Seems to happen when laptop is woken from sleep - I think.

gene/

---------------------------------------------------------

Jun 28 08:49:59 lap3 kernel: [   39.578270]
===================================================
Jun 28 08:49:59 lap3 kernel: [   39.578272] [ INFO: suspicious
rcu_dereference_check() usage. ]
Jun 28 08:49:59 lap3 kernel: [   39.578274]
---------------------------------------------------
Jun 28 08:49:59 lap3 kernel: [   39.578275]
security/selinux/netport.c:143 invoked rcu_dereference_check() withou
t protection!
Jun 28 08:49:59 lap3 kernel: [   39.578277]
Jun 28 08:49:59 lap3 kernel: [   39.578277] other info that might help
us debug this:
Jun 28 08:49:59 lap3 kernel: [   39.578278]
Jun 28 08:49:59 lap3 kernel: [   39.578279]
Jun 28 08:49:59 lap3 kernel: [   39.578280] rcu_scheduler_active = 1,
debug_locks = 0
Jun 28 08:49:59 lap3 kernel: [   39.578281] 1 lock held by named/1247:
Jun 28 08:49:59 lap3 kernel: [   39.578282]  #0:
(sel_netport_lock){+.....}, at: [<ffffffff812193a6>] sel_netpor
t_sid+0xa1/0x207
Jun 28 08:49:59 lap3 kernel: [   39.578291]
Jun 28 08:49:59 lap3 kernel: [   39.578291] stack backtrace:
Jun 28 08:49:59 lap3 kernel: [   39.578293] Pid: 1247, comm: named Not
tainted 3.0-0.rc5.git0.1.fc16.x86_64 #1
Jun 28 08:49:59 lap3 kernel: [   39.578295] Call Trace:
Jun 28 08:49:59 lap3 kernel: [   39.578300]  [<ffffffff81086e4d>]
lockdep_rcu_dereference+0xa8/0xb0
Jun 28 08:49:59 lap3 kernel: [   39.578303]  [<ffffffff812194a0>]
sel_netport_sid+0x19b/0x207
Jun 28 08:49:59 lap3 kernel: [   39.578306]  [<ffffffff81219305>] ?
sel_netport_find+0x93/0x93
Jun 28 08:49:59 lap3 kernel: [   39.578309]  [<ffffffff8121382f>]
selinux_socket_bind+0x12a/0x26f
Jun 28 08:49:59 lap3 kernel: [   39.578311]  [<ffffffff81089296>] ?
lock_release+0x173/0x19c
Jun 28 08:49:59 lap3 kernel: [   39.578316]  [<ffffffff81105751>] ?
might_fault+0xa5/0xac
Jun 28 08:49:59 lap3 kernel: [   39.578318]  [<ffffffff81105708>] ?
might_fault+0x5c/0xac
Jun 28 08:49:59 lap3 kernel: [   39.578322]  [<ffffffff8120d867>]
security_socket_bind+0x16/0x18
Jun 28 08:49:59 lap3 kernel: [   39.578326]  [<ffffffff813f86b7>]
sys_bind+0x73/0xcf
Jun 28 08:49:59 lap3 kernel: [   39.578329]  [<ffffffff814fa1ba>] ?
sysret_check+0x2e/0x69
Jun 28 08:49:59 lap3 kernel: [   39.578332]  [<ffffffff81089781>] ?
trace_hardirqs_on_caller+0x10b/0x12f
Jun 28 08:49:59 lap3 kernel: [   39.578336]  [<ffffffff810ac3c9>] ?
audit_syscall_entry+0x11c/0x148
Jun 28 08:49:59 lap3 kernel: [   39.578339]  [<ffffffff8125cbae>] ?
trace_hardirqs_on_thunk+0x3a/0x3f
Jun 28 08:49:59 lap3 kernel: [   39.578342]  [<ffffffff814fa182>]
system_call_fastpath+0x16/0x1b