From: Thomas Gleixner <tglx@linutronix.de>
To: Nix <nix@esperi.org.uk>
Cc: Andres Salomon <dilinger@queued.net>,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: 4.4.1 regression from 4.1.x: Soekris net5501 crash in IRQ after mfgpt timer initialization
Date: Tue, 2 Feb 2016 16:51:38 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1602021650010.25254@nanos> (raw)
In-Reply-To: <8760y7cfxq.fsf@esperi.org.uk>
On Tue, 2 Feb 2016, Nix wrote:
> On 2 Feb 2016, Thomas Gleixner said:
>
> > On Tue, 2 Feb 2016, Nix wrote:
> >
> >> [Cc:ed Thomas on the vague hope that maybe this is osmething to do with
> >> the IRQ subsystem in general, though I doubt it, since only the one
> >> machine is crashing for me: it's probably the CS5531's interactions
> >> with said subsystem at fault.]
> >
> > Kinda. That driver does the following:
> >
> > setup the irq in CS5531
> >
> > request the interrupt to install the handler
> >
> > register the clockevents device
>
> It seems like it should do those in the opposite order, really, or at
> the very least do the IRQ setup last!
Yes.
> > So the interrupt hits before the clockevent device is registered and the event
> > handler is installed. So mfgpt_tick() will happily call a null pointer.
> >
> > The patch below should fix^Wwork around the issue.
>
> The fairly trivial code motion below also seems to work, and may be more
> like an actual fix, though I'm a bit horrified that it's this simple. I
> may well have moved too much and unknowingly violated some invariant.
I was lazy and did not do this, because it wreckages the error pathes. So I
went for the workaround in the hope that the authors of that stuff will take
care :)
Thanks,
tglx
next prev parent reply other threads:[~2016-02-02 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 14:21 Nix
2016-02-02 14:40 ` Thomas Gleixner
2016-02-02 15:03 ` Nix
2016-02-02 15:51 ` Thomas Gleixner [this message]
2016-02-02 16:07 ` Nix
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=alpine.DEB.2.11.1602021650010.25254@nanos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=dilinger@queued.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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®