mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, Brandon Philips <brandon@ifup.org>,
	linux-kernel@vger.kernel.org, Brice Goglin <brice@myri.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Robert Love <rml@novell.com>
Subject: Re: [patch] genirq/MSI: restore __do_IRQ() compat logic temporarily
Date: Tue, 12 Sep 2006 08:37:42 -0600	[thread overview]
Message-ID: <m14pvd6thl.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060912075047.GA10641@elte.hu> (Ingo Molnar's message of "Tue, 12 Sep 2006 09:50:47 +0200")

Ingo Molnar <mingo@elte.hu> writes:

> * Eric W. Biederman <ebiederm@xmission.com> wrote:
>
>> Ok.  Looking at it I almost certain the problem is that
>> we lost the hunk of code removed in: 266f0566761cf88906d634727b3d9fc2556f5cbd
>> i386: Fix stack switching in do_IRQ
>> 
>> -       if (!irq_desc[irq].handle_irq) {
>> -               __do_IRQ(irq, regs);
>> -               goto out_exit;
>> -       }
>> 
>> The msi code does not yet set desc->handle_irq.  So when we attempt to 
>> call it we get a NULL pointer dereference.
>
> indeed ... We thought the MSI cleanup went all the way with the irqchips 
> conversion, that's we suggested to Andrew to drop this chunk in -mm too.

Sorry.  At the time I was trying for a minimal fix to much more
fundamental brain damage.

>> Except for adding that hunk back in and breaking 4K stacks I don't 
>> have an immediate fix.
>
> i've attached a bandaid patch for -mm below. Brandon, does this solve 
> the crash you are seeing?
>
>> I do have a pending cleanup that should result in us setting 
>> handle_irq in all cases.  I will see if I can advance that shortly.
>
> yeah, that's the right solution.

The core problem at the moment is that the generic code in msi.c
still knows about apics.  So struct irq_chip needs to be pushed
to the individual architectures.  At which point it becomes easy to
ensure we have a proper handle_irq value as we aren't trying to be
impossibly generic.

Eric

      parent reply	other threads:[~2006-09-12 14:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 17:44 2.6.18-rc6-mm1 2.6.18-rc5-mm1 Kernel Panic on X60s Brandon Philips
2006-09-08 19:13 ` Andrew Morton
2006-09-08 19:43   ` Brandon Philips
2006-09-08 19:50     ` Andrew Morton
2006-09-09  2:22       ` Benoit Boissinot
2006-09-09  3:27       ` Eric W. Biederman
2006-09-09  5:21         ` Andrew Morton
2006-09-09  5:47           ` Brice Goglin
2006-09-09  6:01             ` Brandon Philips
2006-09-09  6:14               ` Brice Goglin
2006-09-11  2:14       ` Brandon Philips
2006-09-11 16:51         ` Andrew Morton
2006-09-11 17:55           ` Eric W. Biederman
2006-09-12  6:20           ` Eric W. Biederman
2006-09-12  7:50             ` [patch] genirq/MSI: restore __do_IRQ() compat logic temporarily Ingo Molnar
2006-09-12 12:44               ` Brandon Philips
2006-09-12 14:37               ` Eric W. Biederman [this message]

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=m14pvd6thl.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=akpm@osdl.org \
    --cc=brandon@ifup.org \
    --cc=brice@myri.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@novell.com \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®