From: Igor Mammedov <imammedo@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: xen: Clear IRQ_GUEST bit from irq_desc status if its action is NULL
Date: Tue, 13 Sep 2011 14:31:59 +0200 [thread overview]
Message-ID: <4E6F4D3F.7060904@redhat.com> (raw)
In-Reply-To: <4E6F5E830200007800055D49@nat28.tlf.novell.com>
On 09/13/2011 01:45 PM, Jan Beulich wrote:
>>>> On 13.09.11 at 11:08, Igor Mammedov<imammedo@redhat.com> wrote:
>> On a system with Intel C600 series Patsburg SAS controller
>> if following command are executed:
>>
>> rmmod isci
>> modprobe isci
>>
>> the host will crash in pirq_guest_bind in attempt to dereference
>> NULL action pointer.
>>
>> This is caused by isci driver which does not cleanup irq properly,
>> removing device first and then os tries to unbind its irqs afterwards.
>>
>> c/s 20093 and 20844 fixed host crashes when removing isci module.
>>
>> However in dynamic_irq_cleanup 'action' field of irq_desc is set to
>> NULL but IRQ_GUEST flag in 'status' field is not cleared. So on next
>
> So why don't you clear the bit there?
>
>> attempt to bind pirq (modprobe isci) with IRQ_GUEST flag set, branch
>> if ( !(desc->status& IRQ_GUEST) )
>> is skipped and host ends up with dereferencing NULL pointer 'action'.
>>
>> Second hunk is a bit of code cleanup, removing duplicate code and keeps
>> IRQ_GUEST flag reset at one place.
>
> This is not just cleanup - till now, when action == NULL, the function
> would return 0, while with your patch it would return 1 (which is wrong
> afaict), so you'll minimally need to move down the unbind: label by one
> line. But the cleanup here would better be a separate patch anyway.
>
> Jan
Thanks for review.
I'll fix it and re-post it as 2 patches.
>
>> Please review.
>>
>> Signed-off-by: Igor Mammedov<imammedo@redhat.com>
>>
>> diff -r 0312575dc35e xen/arch/x86/irq.c
>> --- a/xen/arch/x86/irq.c Thu Sep 08 15:13:06 2011 +0100
>> +++ b/xen/arch/x86/irq.c Tue Sep 13 09:27:12 2011 +0200
>> @@ -1472,6 +1472,7 @@ static irq_guest_action_t *__pirq_guest_
>>
>> if ( unlikely(action == NULL) )
>> {
>> + desc->status&= ~IRQ_GUEST;
>> dprintk(XENLOG_G_WARNING, "dom%d: pirq %d: desc->action is NULL!\n",
>> d->domain_id, pirq->pirq);
>> return NULL;
>> @@ -1598,17 +1599,14 @@ static int pirq_guest_force_unbind(struc
>>
>> action = (irq_guest_action_t *)desc->action;
>> if ( unlikely(action == NULL) )
>> - {
>> - dprintk(XENLOG_G_WARNING, "dom%d: pirq %d: desc->action is NULL!\n",
>> - d->domain_id, pirq->pirq);
>> - goto out;
>> - }
>> + goto unbind;
>>
>> for ( i = 0; (i< action->nr_guests)&& (action->guest[i] != d); i++ )
>> continue;
>> if ( i == action->nr_guests )
>> goto out;
>>
>> + unbind:
>> bound = 1;
>> oldaction = __pirq_guest_unbind(d, pirq, desc);
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
Thanks,
Igor
next prev parent reply other threads:[~2011-09-13 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 9:08 xen: Clear IRQ_GUEST bit from irq_desc status if its action is NULL Igor Mammedov
2011-09-13 11:45 ` Jan Beulich
2011-09-13 12:31 ` Igor Mammedov [this message]
2011-09-13 12:36 ` Igor Mammedov
2011-09-13 13:10 ` Jan Beulich
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=4E6F4D3F.7060904@redhat.com \
--to=imammedo@redhat.com \
--cc=xen-devel@lists.xensource.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 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.