mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, dwalker@mvista.com, mingo@elte.hu
Subject: Re: [PATCH] RT: Invert some TRACE_BUG_ON_LOCKED tests
Date: Fri, 02 Sep 2005 18:40:52 -0400	[thread overview]
Message-ID: <1125700852.5601.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20050902200856.GY3966@smtp.west.cox.net>

On Fri, 2005-09-02 at 13:08 -0700, Tom Rini wrote:
> With 2.6.13-rt4 I had to do the following in order to get my paired down
> config booting on my x86 whitebox (defconfig works fine, after I enable
> enet/8250_console/nfsroot).  Daniel Walker helped me trace this down.


Tom,

TRACE_BUG_ON_LOCKED(!spin_is_locked(&lock->wait_lock));

_is_ correct.  Those locks must be locked at those cases.  If it isn't
then we wan't to trigger a bug.  Hence the "BUG_ON" part.  You can never
guarantee that a lock will be unlock since another process on another
CPU might have it.

Now if you are getting a BUG, where as one of these places the lock is
_not_ held, then that's a bug.

Hmm, I wonder if these should be switched to __raw_spin_is_locked.

Oh wait, is this a UP system?  Shoot, spin_is_locked on UP is defined as
zero so this _would_ trigger. Ouch!

Ingo, I guess we need a TRACE_BUG_ON_LOCKED_SMP() macro.

-- Steve




  reply	other threads:[~2005-09-02 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02 20:00 [PATCH] RT: set LPPTEST default to off Daniel Walker
2005-09-02 20:08 ` [PATCH] RT: Invert some TRACE_BUG_ON_LOCKED tests Tom Rini
2005-09-02 22:40   ` Steven Rostedt [this message]
2005-09-02 22:53     ` Steven Rostedt
2005-09-06 15:16       ` Tom Rini
2005-09-12 13:43   ` Ingo Molnar
2005-09-12 13:47     ` Ingo Molnar

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=1125700852.5601.16.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=trini@kernel.crashing.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

Powered by JetHome