From: 'Christoph Hellwig' <hch@infradead.org>
To: "Smart, James" <James.Smart@Emulex.Com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
Anton Blanchard <anton@samba.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [Emulex] queuecommands and GFP_ATOMIC
Date: Tue, 8 Jun 2004 19:23:56 +0100 [thread overview]
Message-ID: <20040608182356.GA7523@infradead.org> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF28034F946C@xbl.ma.emulex.com>
On Tue, Jun 08, 2004 at 02:21:05PM -0400, Smart, James wrote:
> So we've done some testing with the locks moved and the GFP_xxx flag
> changed...
>
> On a RedHat 3.90 2.6.5 kernel, we hit the following:
>
> Debug: sleeping function called from invalid context at mm/slab.c:1980
> in_atomic():1, irqs_disabled():0
> Call Trace:
Looks like you used spin_unlock instead of spin_unlock_irq for the host
lock.
next prev parent reply other threads:[~2004-06-08 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 18:21 [Emulex] queuecommands and GFP_ATOMIC Smart, James
2004-06-08 18:23 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 19:06 Smart, James
2004-06-08 19:09 ` 'Christoph Hellwig'
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=20040608182356.GA7523@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.Com \
--cc=anton@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox