From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: lockdep warning looks scsi related
Date: Fri, 06 Oct 2006 15:22:43 +0200 [thread overview]
Message-ID: <1160140963.3000.106.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061005100853.4d65dc90@dxpl.pdx.osdl.net>
On Thu, 2006-10-05 at 10:08 -0700, Stephen Hemminger wrote:
> This is current main linux-2.6 (git pulled yesterday).
> Running on 2 CPU Opteron
> Happened during overnight (beagle cronjob?)
hmm lots of changes in cfq, and to be honest the
cfq_exit_single_io_context() change makes me nervous.
The comment says it's called with interrupts disabled, what the comment
does NOT say is that this function ENABLES interrupts!
(the entire cfq change has many places where interrupts now get enabled
where previously they remained as is... )
next prev parent reply other threads:[~2006-10-06 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 17:08 lockdep warning looks scsi related Stephen Hemminger
2006-10-06 13:22 ` Arjan van de Ven [this message]
2006-10-06 17:19 ` Jens Axboe
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=1160140963.3000.106.camel@laptopd505.fenrus.org \
--to=arjan@fenrus.demon.nl \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=shemminger@osdl.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