From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: stable@kernel.org, Dominik Brodowski <linux@dominikbrodowski.net>,
linux-wireless@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH 2.6.32.y] hostap_cs: fix sleeping function called from invalid context
Date: Tue, 18 Jan 2011 16:43:05 +0100 [thread overview]
Message-ID: <20110118154305.GA2448@redhat.com> (raw)
In-Reply-To: <4D35A87D.3020600@canonical.com>
On Tue, Jan 18, 2011 at 07:49:33AM -0700, Tim Gardner wrote:
> Yes - I think this patch is correct. I didn't drill deep enough to
> notice the GFP_KERNEL memory allocation. However, I think there is
> still a problem with the interrupt handler which will only be
> noticed if there is another active device on the same shared
> interrupt. Shouldn't it return IRQ_NONE? See attached.
I'm not sure. I think kernel could disable interrupt line when IRQ_NONE
is returned, but line is not shared.
Generally hostap pcmcia initialization procedure does not look correct.
It should be rahter rearranged to request irq when we are ready to
receive it, like that:
ret = pcmcia_enable_device(link);
if (ret)
goto failed;
dev->irq = link->irq;
dev->base_addr = link->resource[0]->start;
ret = pcmcia_request_irq(link, prism2_interrupt);
if (ret)
goto failed;
However I'm not sure if pcmcia_enable_device() does not require
to have pcmcia_request_irq() before?
Stanislaw
next prev parent reply other threads:[~2011-01-18 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 13:05 [PATCH 2.6.32.y] hostap_cs: fix sleeping function called from invalid context Stanislaw Gruszka
2011-01-18 14:49 ` Tim Gardner
2011-01-18 15:43 ` Stanislaw Gruszka [this message]
2011-01-18 21:10 ` Tim Gardner
2011-01-19 7:36 ` Stanislaw Gruszka
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=20110118154305.GA2448@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=stable@kernel.org \
--cc=tim.gardner@canonical.com \
/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).