From: Andrew Morton <akpm@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: linux-scsi@vger.kernel.org, olh@suse.de
Subject: Re: Fw: blk_cleanup_queue, sleep in invalid context
Date: Wed, 4 Jan 2006 17:12:56 -0800 [thread overview]
Message-ID: <20060104171256.2c44a40e.akpm@osdl.org> (raw)
In-Reply-To: <20060105005609.GA17604@kroah.com>
Greg KH <greg@kroah.com> wrote:
>
> On Wed, Jan 04, 2006 at 04:53:00PM -0800, Andrew Morton wrote:
> >
> > Looks like scsi is the culprit here - doing put_device() from softirq.
> >
> > Greg, what are the rules here? Can we enforce them with a highest-level
> > might_sleep()?
>
> You mean, put a might_sleep() in put_device()? Yes, I can do that, as
> that function might sleep.
Yep. And in any other high-level device management entrypoints which you
can think of.
> SCSI is the culprit here, and I thought that
> the scsi developers had fixed this up already.
It seems to be resisting arrest.
next prev parent reply other threads:[~2006-01-05 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 0:53 Fw: blk_cleanup_queue, sleep in invalid context Andrew Morton
2006-01-05 0:56 ` Greg KH
2006-01-05 1:12 ` Andrew Morton [this message]
2006-01-05 12:52 ` Olaf Hering
2006-01-05 17:08 ` James Bottomley
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=20060104171256.2c44a40e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.de \
/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