From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: Austin Schuh <austin@peloton-tech.com>,
rt-users <linux-rt-users@vger.kernel.org>, xfs <xfs@oss.sgi.com>,
Philipp Schrader <philipp@peloton-tech.com>,
Brian Silverman <brian@peloton-tech.com>
Subject: Re: [RT XFS] BUG from lockdep in xfs
Date: Mon, 14 Sep 2015 09:50:59 +1000 [thread overview]
Message-ID: <20150913235059.GU26895@dastard> (raw)
In-Reply-To: <20150909114451.GA30015@bfoster.bfoster>
On Wed, Sep 09, 2015 at 07:44:51AM -0400, Brian Foster wrote:
> On Tue, Sep 08, 2015 at 11:54:07PM -0700, Austin Schuh wrote:
> > I'm running xfstests and got the following BUG with lockdep enabled.
> > I'm running the 4.1.6-rt5 kernel from TI's tree on a TI ARM chip.
> >
> > Any ideas on what could be causing it, or if it is a real problem?
> >
> > I see some patches in Dave's latest 4.3 pull request that discuss
> > lockdep. Are there any ones there that are worth backporting to my
> > 4.1.6 kernel?
> >
>
> I suspect Dave's recent rework of the lockdep namespace bits is what you
> want:
>
> 0952c818 xfs: clean up inode lockdep annotations
Yes, that works around the issue that causes this:
> > [ 4357.394974] BUG: looking up invalid subclass: 8
i.e. that we have about 15 different subclass annotations for
different inode locking situations we need to shoe horn into 8
subclasses...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-09-13 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 6:54 [RT XFS] BUG from lockdep in xfs Austin Schuh
2015-09-09 11:44 ` Brian Foster
2015-09-13 23:50 ` Dave Chinner [this message]
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=20150913235059.GU26895@dastard \
--to=david@fromorbit.com \
--cc=austin@peloton-tech.com \
--cc=bfoster@redhat.com \
--cc=brian@peloton-tech.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=philipp@peloton-tech.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).