linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>, Mark Lord <liml@rtr.ca>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
Date: Mon, 30 Oct 2006 19:03:57 +0100	[thread overview]
Message-ID: <20061030180357.GD14055@kernel.dk> (raw)
In-Reply-To: <20061030175400.GA31581@elte.hu>

On Mon, Oct 30 2006, Ingo Molnar wrote:
> 
> * Jens Axboe <jens.axboe@oracle.com> wrote:
> 
> > > > things may be allocated from that path, so we pass gfp_mask around. I'll
> > > > double check it tonight, but I don't currently see what could be wrong.
> > > > Would lockdep complain about:
> > > > 
> > > >         spin_lock_irqsave(lock, flags);
> > > >         ...
> > > >         spin_unlock_irq(lock);
> > > >         ...
> > > >         spin_lock_irq(lock);
> > > >         ...
> > > >         spin_unlock_irqrestore(lock, flags);
> > > 
> > > this is fine for lockdep IF and only IF there is no "out lock" held
> > > around this that requires irqs to be off. So if you do
> > > 
> > > spin_lock_irqsave(lock1, flags);
> > > ...
> > > spin_lock_irqsave(lock2, flags);
> > > spin_unlock_irq(lock2)
> > > ...
> > > 
> > > then lockdep WILL complain, and rightfully so, about a violation since
> > > lock1 gets violated here ;)
> > 
> > Naturally, that is a bug fair and simple, nothing to do with lockdep.
> 
> well, finding such locking bugs is the main purpose of lockdep, so there 
> is at least some connection i'd say ;-)

Right, I'm totally with you on that one, I wasn't trying to state
otherwise :-)

But we've also had a class of lockdep complaints that simply need some
sort of annotation so that lockdep understands there's nothing wrong
with it.

-- 
Jens Axboe


  reply	other threads:[~2006-10-30 18:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 14:33 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state Mark Lord
2006-10-30 14:43 ` Jens Axboe
2006-10-30 14:57   ` Arjan van de Ven
2006-10-30 15:44     ` Jens Axboe
2006-10-30 16:16       ` Arjan van de Ven
2006-10-30 16:26         ` Jens Axboe
2006-10-30 16:31           ` Arjan van de Ven
2006-10-30 17:52             ` Jens Axboe
2006-10-30 17:54               ` Ingo Molnar
2006-10-30 18:03                 ` Jens Axboe [this message]
2006-10-30 17:54               ` Mark Lord
2006-10-30 18:11                 ` Mark Lord
2006-10-30 18:16                   ` Jens Axboe
2006-10-30 18:30                     ` Mark Lord
2006-10-30 18:35                       ` Mark Lord
2006-10-30 18:45                       ` Arjan van de Ven
2006-10-30 18:56                         ` Jens Axboe
2006-10-30 18:52                       ` Jens Axboe
2006-10-30 18:59                         ` Mark Lord
2006-10-30 19:04                           ` Jens Axboe
2006-10-30 18:20                   ` Mark Lord
2006-10-30 17:56               ` Arjan van de Ven
2006-10-30 17:57                 ` 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=20061030180357.GD14055@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=arjan@infradead.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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).