From: Nick Bowler <nbowler@elliptictech.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, autofs@linux.kernel.org,
Ian Kent <raven@themaw.net>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Lockdep splat in autofs with 2.6.39-rc2
Date: Wed, 27 Apr 2011 09:22:19 -0400 [thread overview]
Message-ID: <20110427132219.GA2843@elliptictech.com> (raw)
In-Reply-To: <20110421212537.GC24898@home.goodmis.org>
On 2011-04-21 17:25 -0400, Steven Rostedt wrote:
> On Thu, Apr 07, 2011 at 03:44:03PM -0400, Nick Bowler wrote:
> > Just saw this on 2.6.39-rc2 after half a day or so of uptime. I've
> > never seen it before today so it may be a regression from 2.6.38.
> > Nothing seems have failed as a result. Please let me know if you
> > need any more info.
>
> Could you try this patch. I know it may be hard to reproduce, but the
> issue is that we are recursing down the locks in a tree/list and we changed a
> lock from being nested to being a parent. This patch tells lockdep about
> what we did.
OK, I've built 2.6.39-rc5 with this patch applied. However, it took ~5
days before I saw any splat with -rc4, thus it's unlikely that I'll be
able to say for sure that it works.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-04-27 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 19:44 Lockdep splat in autofs with 2.6.39-rc2 Nick Bowler
2011-04-13 19:26 ` Maciej Rutecki
2011-04-13 19:43 ` Nick Bowler
2011-04-14 19:38 ` Maciej Rutecki
2011-04-14 19:38 ` Maciej Rutecki
2011-04-21 21:25 ` Steven Rostedt
2011-04-27 13:22 ` Nick Bowler [this message]
2011-05-11 19:13 ` Nick Bowler
2011-06-14 0:43 ` Steven Rostedt
2011-06-20 14:48 ` Nick Bowler
2011-07-25 2:46 ` [autofs] " Ian Kent
2011-07-25 12:33 ` Steven Rostedt
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=20110427132219.GA2843@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=raven@themaw.net \
--cc=rostedt@goodmis.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 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.