From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: [-next] fs/eventpoll.c:545 suspicious rcu_dereference_check() usage Date: Fri, 22 Mar 2013 13:42:48 +0300 Message-ID: <20130322104248.GA2589@swordfish.minsk.epam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Alexander Viro Return-path: Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello, got this with today's linux-next [ 3.163894] =============================== [ 3.163895] [ INFO: suspicious RCU usage. ] [ 3.163897] 3.9.0-rc3-next-20130322-dbg-dirty #1 Not tainted [ 3.163898] ------------------------------- [ 3.163900] fs/eventpoll.c:545 suspicious rcu_dereference_check() usage! [ 3.163900] other info that might help us debug this: [ 3.163902] rcu_scheduler_active = 1, debug_locks = 1 [ 3.163903] 2 locks held by ata_id/763: [ 3.163915] #0: (&pipe->wait){......}, at: [] __wake_up_sync_key+0x37/0x80 [ 3.163923] #1: (&(&ep->lock)->rlock){......}, at: [] ep_poll_callback+0x59/0x1f0 [ 3.163924] stack backtrace: [ 3.163927] Pid: 763, comm: ata_id Not tainted 3.9.0-rc3-next-20130322-dbg-dirty #1 [ 3.163929] Call Trace: [ 3.163940] [] lockdep_rcu_suspicious+0xe6/0x130 [ 3.163945] [] ep_poll_callback+0x1cf/0x1f0 [ 3.163949] [] __wake_up_common+0x55/0x90 [ 3.163952] [] __wake_up_sync_key+0x53/0x80 [ 3.163957] [] pipe_write+0x448/0x590 [ 3.163962] [] do_sync_write+0x80/0xb0 [ 3.163965] [] vfs_write+0xa8/0x180 [ 3.163968] [] SyS_write+0x55/0xb0 [ 3.163975] [] system_call_fastpath+0x1a/0x1f -ss