public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: auth_gss.c - rcu dereference warning
Date: Tue, 27 Jul 2010 12:48:38 +0200	[thread overview]
Message-ID: <1280227718.3755.3.camel@jlt3.sipsolutions.net> (raw)

I consistently get this when I unmount an NFS volume.

johannes

[  381.427221] ===================================================
[  381.427225] [ INFO: suspicious rcu_dereference_check() usage. ]
[  381.427228] ---------------------------------------------------
[  381.427232] /home/johannes/sys/wireless-testing/net/sunrpc/auth_gss/auth_gss.c:947 invoked rcu_dereference_check() without protection!
[  381.427236] 
[  381.427237] other info that might help us debug this:
[  381.427238] 
[  381.427241] 
[  381.427242] rcu_scheduler_active = 1, debug_locks = 1
[  381.427246] 2 locks held by rpciod/0/1881:
[  381.427248]  #0:  (rpciod){+.+.+.}, at: [<ffffffff810640cf>] run_workqueue+0x11f/0x3c0
[  381.427262]  #1:  ((&task->u.tk_work)){+.+.+.}, at: [<ffffffff810640cf>] run_workqueue+0x11f/0x3c0
[  381.427271] 
[  381.427272] stack backtrace:
[  381.427276] Pid: 1881, comm: rpciod/0 Not tainted 2.6.35-rc6-wl-47665-gc2e2180-dirty #174
[  381.427280] Call Trace:
[  381.427289]  [<ffffffff8107e494>] lockdep_rcu_dereference+0xa4/0xc0
[  381.427297]  [<ffffffffa05e0191>] gss_free_ctx+0x91/0xa0 [auth_rpcgss]
[  381.427311]  [<ffffffffa05e19ed>] gss_destroy_nullcred+0x4d/0x70 [auth_rpcgss]
[  381.427331]  [<ffffffffa0598f97>] put_rpccred+0x127/0x140 [sunrpc]
[  381.427348]  [<ffffffffa059922e>] rpcauth_unbindcred+0x2e/0x70 [sunrpc]
[  381.427371]  [<ffffffffa05970ea>] rpc_put_task+0x3a/0xd0 [sunrpc]
[  381.427386]  [<ffffffffa0597810>] rpc_release_task+0x70/0xa0 [sunrpc]
[  381.427402]  [<ffffffffa0598229>] __rpc_execute+0x179/0x200 [sunrpc]
[  381.427433]  [<ffffffffa05982f5>] rpc_async_schedule+0x15/0x20 [sunrpc]
[  381.427438]  [<ffffffff81064120>] run_workqueue+0x170/0x3c0
[  381.427457]  [<ffffffff81064413>] worker_thread+0xa3/0x110
[  381.427472]  [<ffffffff81069386>] kthread+0x96/0xa0
[  381.427479]  [<ffffffff81003514>] kernel_thread_helper+0x4/0x10



             reply	other threads:[~2010-07-27 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 10:48 Johannes Berg [this message]
2010-07-31 19:20 ` auth_gss.c - rcu dereference warning Trond Myklebust
2010-08-01 19:41   ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1280227718.3755.3.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox