From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: sleeping function called from invalid context at arch/arm/mm/fault.c:301
Date: Wed, 18 Sep 2013 16:07:30 +0100 [thread overview]
Message-ID: <20130918150730.GU12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <m3ioxy9tck.fsf@t19.piap.pl>
On Wed, Sep 18, 2013 at 03:01:31PM +0200, Krzysztof Ha?asa wrote:
> Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> > I suspect it's this great bit of coding in free_solo_dev():
>
> /* Now cleanup the PCI device */
> solo_irq_off(solo_dev, ~0);
> pci_iounmap(pdev, solo_dev->reg_base);
> if (pdev->irq)
> free_irq(pdev->irq, solo_dev);
>
> solo_irq_off() tries to disable IRQ by masking the hw line but I guess
> there may be some time window in which a problem may show up.
> Anyway, there is no reason to unmap registers before free_irq().
Except that it's part of debugging shared interrupts.
Remember, any driver which is still hooked into the IRQ handling subsystem
with a shared interrupt can still receive an interrupt at any moment due
to another device on that shared interrupt line raising its request.
So, in order to find buggy drivers, the IRQ layer will call a shared
interrupt handler immediately upon registration, and also upon freeing.
So, it's not a spurious IRQ, it's an attempt by the IRQ layer to find
buggy drivers, and it's done exactly that. It's working as designed.
next prev parent reply other threads:[~2013-09-18 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 8:54 BUG: sleeping function called from invalid context at arch/arm/mm/fault.c:301 Krzysztof Hałasa
2013-09-18 9:41 ` Russell King - ARM Linux
2013-09-18 13:01 ` Krzysztof Hałasa
2013-09-18 15:07 ` Russell King - ARM Linux [this message]
2013-09-18 21:00 ` Krzysztof Halasa
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=20130918150730.GU12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).