From: Alexander Gordeev <agordeev@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Milburn <dmilburn@redhat.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libahci: ahci interrupt check for disabled port since private_data may be NULL
Date: Wed, 16 Apr 2014 20:51:05 +0200 [thread overview]
Message-ID: <20140416185105.GA21640@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <20140416151932.GF1257@htj.dyndns.org>
On Wed, Apr 16, 2014 at 11:19:32AM -0400, Tejun Heo wrote:
> > Also, we're not going to see complains on spurious interrupts, aren't we?
>
> The irq isn't even requested, it won't reach the kernel at all.
The crash occured in ahci_hw_interrupt() which means multiple MSIs
were enabled. The fact driver does not request IRQ does not mean
the PCI device does not send an MSI interrupt (and it does as we're
observing the crash). So my question if the dummy port interrupt
does not end up in handle_bad_irq() or some?
Thanks!
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-04-16 18:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 21:47 [PATCH] libahci: ahci interrupt check for disabled port since private_data may be NULL David Milburn
2014-04-15 16:33 ` Tejun Heo
2014-04-15 18:18 ` David Milburn
2014-04-15 18:20 ` Tejun Heo
2014-04-16 7:39 ` Alexander Gordeev
2014-04-16 15:19 ` Tejun Heo
2014-04-16 16:28 ` David Milburn
2014-04-16 18:51 ` Alexander Gordeev [this message]
2014-04-16 19:14 ` Tejun Heo
2014-04-17 8:29 ` Alexander Gordeev
2014-04-17 13:29 ` Tejun Heo
2014-04-17 12:44 ` Alexander Gordeev
2014-04-17 13:45 ` Tejun Heo
2014-04-17 13:07 ` Alexander Gordeev
2014-04-17 14:09 ` Tejun Heo
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=20140416185105.GA21640@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=dmilburn@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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.