All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: INFO: suspicious rcu_dereference_check()
Date: Mon, 29 Mar 2010 08:25:57 -0700	[thread overview]
Message-ID: <20100329152557.GD2569@linux.vnet.ibm.com> (raw)
In-Reply-To: <1269531400.3648.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Thu, Mar 25, 2010 at 11:36:40AM -0400, Trond Myklebust wrote:
> On Thu, 2010-03-25 at 11:48 +0100, Zdenek Kabelac wrote: 
> > Hi
> > 
> > I've enabled rcu correctness for my  todays 2.6.34-rc2 kernel.
> > 
> > I'm getting this INFO: from my kvm guest (which uses host's nfs
> > exported directory.)
> > This
> > 
> > ===================================================
> > [ INFO: suspicious rcu_dereference_check() usage. ]
> > ---------------------------------------------------
> > fs/nfs/delegation.c:348 invoked rcu_dereference_check() without protection!
> > 
> > other info that might help us debug this:
> > 
> > 
> > rcu_scheduler_active = 1, debug_locks = 0
> > 2 locks held by rm/1820:
> >  #0:  (&sb->s_type->i_mutex_key#13/1){+.+.+.}, at:
> > [<ffffffff81138e1b>] do_unlinkat+0x9b/0x1c0
> >  #1:  (&sb->s_type->i_mutex_key#13){+.+.+.}, at: [<ffffffff81136a76>]
> > vfs_unlink+0x56/0xf0
> > 
> > stack backtrace:
> > Pid: 1820, comm: rm Not tainted 2.6.34-rc2-00186-ge79a302 #60
> > Call Trace:
> >  [<ffffffff810819fb>] lockdep_rcu_dereference+0xbb/0xc0
> >  [<ffffffffa0228351>] nfs_inode_return_delegation+0x101/0x110 [nfs]
> >  [<ffffffffa01fd58d>] nfs_unlink+0xad/0x2a0 [nfs]
> >  [<ffffffff81136aba>] vfs_unlink+0x9a/0xf0
> >  [<ffffffff81148365>] ? mnt_want_write+0x65/0xb0
> >  [<ffffffff81138f03>] do_unlinkat+0x183/0x1c0
> >  [<ffffffff8142b66d>] ? retint_swapgs+0xe/0x13
> >  [<ffffffff81083985>] ? trace_hardirqs_on_caller+0x155/0x1a0
> >  [<ffffffff8142a232>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> >  [<ffffffff811390a2>] sys_unlinkat+0x22/0x40
> >  [<ffffffff81031dc8>] sysenter_dispatch+0x7/0x2c
> > 
> 
> It is a 100% bogus warning. There are tentative patches floating around
> to fix the above warning, but they haven't been merged yet.
> 
> In the meantime, please ignore...

Did you want to carry these patches, or would you rather that I do so?

(And sorry for the slow response, was on holiday last week.)

							Thanx, Paul

WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: INFO: suspicious rcu_dereference_check()
Date: Mon, 29 Mar 2010 08:25:57 -0700	[thread overview]
Message-ID: <20100329152557.GD2569@linux.vnet.ibm.com> (raw)
In-Reply-To: <1269531400.3648.1.camel@localhost.localdomain>

On Thu, Mar 25, 2010 at 11:36:40AM -0400, Trond Myklebust wrote:
> On Thu, 2010-03-25 at 11:48 +0100, Zdenek Kabelac wrote: 
> > Hi
> > 
> > I've enabled rcu correctness for my  todays 2.6.34-rc2 kernel.
> > 
> > I'm getting this INFO: from my kvm guest (which uses host's nfs
> > exported directory.)
> > This
> > 
> > ===================================================
> > [ INFO: suspicious rcu_dereference_check() usage. ]
> > ---------------------------------------------------
> > fs/nfs/delegation.c:348 invoked rcu_dereference_check() without protection!
> > 
> > other info that might help us debug this:
> > 
> > 
> > rcu_scheduler_active = 1, debug_locks = 0
> > 2 locks held by rm/1820:
> >  #0:  (&sb->s_type->i_mutex_key#13/1){+.+.+.}, at:
> > [<ffffffff81138e1b>] do_unlinkat+0x9b/0x1c0
> >  #1:  (&sb->s_type->i_mutex_key#13){+.+.+.}, at: [<ffffffff81136a76>]
> > vfs_unlink+0x56/0xf0
> > 
> > stack backtrace:
> > Pid: 1820, comm: rm Not tainted 2.6.34-rc2-00186-ge79a302 #60
> > Call Trace:
> >  [<ffffffff810819fb>] lockdep_rcu_dereference+0xbb/0xc0
> >  [<ffffffffa0228351>] nfs_inode_return_delegation+0x101/0x110 [nfs]
> >  [<ffffffffa01fd58d>] nfs_unlink+0xad/0x2a0 [nfs]
> >  [<ffffffff81136aba>] vfs_unlink+0x9a/0xf0
> >  [<ffffffff81148365>] ? mnt_want_write+0x65/0xb0
> >  [<ffffffff81138f03>] do_unlinkat+0x183/0x1c0
> >  [<ffffffff8142b66d>] ? retint_swapgs+0xe/0x13
> >  [<ffffffff81083985>] ? trace_hardirqs_on_caller+0x155/0x1a0
> >  [<ffffffff8142a232>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> >  [<ffffffff811390a2>] sys_unlinkat+0x22/0x40
> >  [<ffffffff81031dc8>] sysenter_dispatch+0x7/0x2c
> > 
> 
> It is a 100% bogus warning. There are tentative patches floating around
> to fix the above warning, but they haven't been merged yet.
> 
> In the meantime, please ignore...

Did you want to carry these patches, or would you rather that I do so?

(And sorry for the slow response, was on holiday last week.)

							Thanx, Paul

  parent reply	other threads:[~2010-03-29 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 10:48 INFO: suspicious rcu_dereference_check() Zdenek Kabelac
     [not found] ` <c4e36d111003250348q678eb2e6w4f3e8133e7fd6e58-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-25 15:36   ` Trond Myklebust
2010-03-25 15:36     ` Trond Myklebust
     [not found]     ` <1269531400.3648.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-03-29 15:25       ` Paul E. McKenney [this message]
2010-03-29 15:25         ` Paul E. McKenney
2010-03-29 17:14         ` Trond Myklebust
     [not found]         ` <1269882883.3181.25.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-03-29 18:56           ` David Howells
2010-03-29 18:56             ` David Howells

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=20100329152557.GD2569@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=zdenek.kabelac@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.