From: Greg KH <gregkh@suse.de>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Andrew Morton <akpm@osdl.org>, Ake <Ake.Sandgren@hpc2n.umu.se>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>,
James Smart <James.Smart@emulex.com>
Subject: Re: 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?)
Date: Wed, 1 Jun 2005 13:39:58 -0700 [thread overview]
Message-ID: <20050601203958.GA3475@suse.de> (raw)
In-Reply-To: <20050601184820.GE22083@plap.qlogic.org>
On Wed, Jun 01, 2005 at 11:48:20AM -0700, Andrew Vasquez wrote:
> On Mon, 30 May 2005, Andrew Morton wrote:
>
> > Ake.Sandgren@hpc2n.umu.se (Ake) wrote:
> > >
> > > Hi!
> > > I got the following when i pulled the FC cable from one of my qla2312
> > > cards.
> > > This is a 2.6.12-rc5 kernel (with udm1 patches for 2.6.12-rc2)
> > >
> > >
> > > May 30 14:12:45 ican-i kernel: [ 1109.864830] qla2300 0000:03:09.0: LOOP DOWN detected.
> > > May 30 14:12:45 ican-i kernel: [ 1109.875948] Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
> > > May 30 14:12:45 ican-i kernel: [ 1109.894492] in_atomic():1, irqs_disabled():1
> > > May 30 14:12:45 ican-i kernel: [ 1109.903864] [dump_stack+30/48] dump_stack+0x1e/0x30
> > > May 30 14:12:45 ican-i kernel: [ 1109.913648] [__might_sleep+167/176] __might_sleep+0xa7/0xb0
> > > May 30 14:12:45 ican-i kernel: [ 1109.924003] [device_for_each_child+35/144] device_for_each_child+0x23/0x90
> > > May 30 14:12:45 ican-i kernel: [ 1109.935865] [pg0+944279047/1069622272] scsi_target_block+0x57/0x60 [scsi_mod]
> > > May 30 14:12:45 ican-i kernel: [ 1109.949142] [pg0+944996009/1069622272] fc_remote_port_block+0x39/0x60 [scsi_transport_fc]
> ...
> >
> > This was reported (and anaylsed) a month ago:
> >
> > http://lkml.org/lkml/2005/4/29/82
> >
> > I don't know if anything has been done about it yet though?
>
> Greg,
>
> Is there some other interrupt-safe alternative:
>
> http://lkml.org/lkml/2005/4/29/129
>
> to using device_for_each_child()? The scsi_target_[block/unblock]()
> functions need to iterate over all the child-scsi_device's belonging
> to an fc_rport.
Did you look at the code in the -mm tree? That's what's going into
2.6.13, so you might have some chance there.
Otherwise you need to rewrite your logic to not do that :)
Good luck,
greg k-h
prev parent reply other threads:[~2005-06-01 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 12:51 2.6.12-rc5: sleeping function called from invalid context (qla2xxx/scsi_transport_fc?) Ake
2005-05-30 21:07 ` Andrew Morton
2005-05-30 21:07 ` Andrew Morton
2005-06-01 18:48 ` Andrew Vasquez
2005-06-01 20:39 ` Greg KH [this message]
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=20050601203958.GA3475@suse.de \
--to=gregkh@suse.de \
--cc=Ake.Sandgren@hpc2n.umu.se \
--cc=James.Bottomley@SteelEye.com \
--cc=James.Smart@emulex.com \
--cc=akpm@osdl.org \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.