Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752072Ab2EOEly (ORCPT ); Tue, 15 May 2012 00:41:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62544 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750801Ab2EOElw (ORCPT ); Tue, 15 May 2012 00:41:52 -0400 Date: Tue, 15 May 2012 00:41:45 -0400 From: Dave Jones To: "Paul E. McKenney" Cc: sds@tycho.nsa.gov, Linux Kernel Subject: suspicious RCU usage in security/selinux/netnode.c Message-ID: <20120515044145.GA21910@redhat.com> Mail-Followup-To: Dave Jones , "Paul E. McKenney" , sds@tycho.nsa.gov, Linux Kernel MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1499 Lines: 39 I just triggered this on Linus' current tree. Dave =============================== [ INFO: suspicious RCU usage. ] 3.4.0-rc7+ #93 Not tainted ------------------------------- security/selinux/netnode.c:178 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 1, debug_locks = 0 1 lock held by trinity/25132: #0: (sel_netnode_lock){+.....}, at: [] sel_netnode_sid+0x148/0x3c0 stack backtrace: Pid: 25132, comm: trinity Not tainted 3.4.0-rc7+ #93 Call Trace: [] lockdep_rcu_suspicious+0xfd/0x130 [] sel_netnode_sid+0x391/0x3c0 [] ? sel_netnode_find+0x1a0/0x1a0 [] selinux_socket_bind+0x104/0x350 [] ? sched_clock_cpu+0xb8/0x130 [] ? sub_preempt_count+0xa9/0xe0 [] security_socket_bind+0x16/0x20 [] sys_bind+0x7a/0x100 [] ? sysret_check+0x22/0x5d [] ? trace_hardirqs_on_caller+0x10d/0x1a0 [] ? __audit_syscall_entry+0xcc/0x310 [] ? trace_hardirqs_on_thunk+0x3a/0x3f [] system_call_fastpath+0x16/0x1b -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/