public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Lock debugging noise or real problem?
Date: Mon, 11 Aug 2008 20:35:07 -0700	[thread overview]
Message-ID: <48A104EB.6040509@tlinx.org> (raw)
In-Reply-To: <48A0F9FC.1070805@sandeen.net>

Eric Sandeen wrote:
> I haven't looked closely at #2 but there have been so many lockdep
> reports for xfs, and so many explanations of why they don't always get
> along, you'll probably be able to find something with some searching.
>   
----

      So in debugging mysterious 'lockups' where I've, at least once, 
noticed a
hangcheck_timer elapse, this lock-checking stuff is just nonsensical?  
It is very
frustrating trying to turn on debug tools in the kernel and get so many 
false positives.

Would it be possible or, perhaps, desirable to eliminate the buggy 
lock-checks in the
xfs code?

Meanwhile...back to finding reasons for the semi-random, periodic hanging...
;^/



  reply	other threads:[~2008-08-12  3:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 19:31 Lock debugging noise or real problem? Linda Walsh
2008-08-11 20:10 ` Eric Sandeen
2008-08-12  2:33   ` Linda Walsh
2008-08-12  2:48     ` Eric Sandeen
2008-08-12  3:35       ` Linda Walsh [this message]
2008-08-12 22:28       ` XFS " Linda A. Walsh
2008-08-13  0:58         ` Dave Chinner
2008-08-13 22:05           ` Linda Walsh
2008-08-14  0:41             ` Dave Chinner
2008-08-14  1:04               ` Linda Walsh

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=48A104EB.6040509@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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