From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: sun4i: Clear interrupts after stopping timer in probe function
Date: Tue, 26 Jul 2016 11:07:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1607261106540.19896@nanos> (raw)
In-Reply-To: <CAGb2v65qoKXO8oQZBMumGZ_VM7KR_236wSNJZMd+VdSGTQu_xQ@mail.gmail.com>
On Tue, 26 Jul 2016, Chen-Yu Tsai wrote:
> On Tue, Jul 26, 2016 at 1:49 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Tue, Jul 26, 2016 at 11:01:59AM +0800, Chen-Yu Tsai wrote:
> >> The bootloader (U-boot) sometimes uses this timer for various delays.
> >> It uses it as a ongoing counter, and does comparisons on the current
> >> counter value. The timer counter is never stopped.
> >>
> >> In some cases when the user interacts with the bootloader, or lets
> >> it idle for some time before loading Linux, the timer may expire,
> >> and an interrupt will be pending. This results in an unexpected
> >> interrupt when the timer interrupt is enabled by the kernel, at
> >> which point the event_handler isn't set yet. This results in a NULL
> >> pointer dereference exception, panic, and no way to reboot.
> >>
> >> Clear any pending interrupts after we stop the timer in the probe
> >> function to avoid this.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >
> > Awesome, thanks!
> >
> > You should put stable in Cc though for this kind of patches.
>
> AFAIK some maintainers prefer to add it themselves. Not sure about
> clocksource so I left it out.
At least you should tell the maintainer, that you consider this to be stable
material. It's not an obvious stable candidate.
Thanks,
tglx
prev parent reply other threads:[~2016-07-26 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 3:01 [PATCH] clocksource: sun4i: Clear interrupts after stopping timer in probe function Chen-Yu Tsai
2016-07-26 5:49 ` Maxime Ripard
2016-07-26 6:42 ` Chen-Yu Tsai
2016-07-26 9:07 ` Thomas Gleixner [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=alpine.DEB.2.11.1607261106540.19896@nanos \
--to=tglx@linutronix.de \
--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