From: David Kozub <zub@linux.fjfi.cvut.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clockevents/drivers/cs5535: improve resilience to spurious interrupts
Date: Fri, 20 Oct 2017 09:38:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1710200930370.3927@linux.fjfi.cvut.cz> (raw)
In-Reply-To: <alpine.DEB.2.20.1710200011111.2054@nanos>
On Fri, 20 Oct 2017, Thomas Gleixner wrote:
> On Thu, 19 Oct 2017, David Kozub wrote:
>
>> This solves a BUG on ALIX 2c3 where mfgpt_tick is called before
>> clockevents_config_and_register returns. This caused mfgpt_tick to call a
>> null function pointer.
>>
>> Thanks to Daniel Lezcano and Thomas Gleixner for helping me analyze this
>> and suggesting a solution.
>
> Thanks for sending this! Though I have two minor issues with this:
>
> 1) The changelog.
>
> We try to structure changelogs by explaining the context, the problem and
> its consequences and the fix. If the fix is non obvious it wants an
> elaborate explanation. Let me give you an example:
>
> The interrupt handler mfgpt_tick() is not robust versus spurious
> interrupts which happen before the clock event device is registered and
> fully initialized.
>
> The reason is that the safe guard against spurious interrupts solely
> checks for the clockevents shutdown state, but lacks a check for
> detached state. If the interrupt hits while the device is in detached
> state it passes the safe guard and dereferences the event handler call
> back which is NULL.
>
> Add the missing state check.
>
> See?
Thanks for the feedback. Yes, that is better.
Now that I'm neither the author of the code nor the author of the commit
message it doesn't seem right that I should be submitting this.
>> - if (clockevent_state_shutdown(&cs5535_clockevent))
>> + if (clockevent_state_detached(&cs5535_clockevent) ||
>> + clockevent_state_shutdown(&cs5535_clockevent))
>
> Please do not use random indentation for multiline conditionals
>
> if (clockevent_state_detached(&cs5535_clockevent) ||
> clockevent_state_shutdown(&cs5535_clockevent))
>
> is the style we use through out the code.
OK. I noticed the four spaces. I was swayed by process/coding-style.rst:
Outside of comments, documentation and except in Kconfig, spaces are never
used for indentation,
But now I think I just misunderstood that. The spaces on the second line
of the "if" are not regarded as ident.
Best regards,
David
next prev parent reply other threads:[~2017-10-20 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:57 David Kozub
2017-10-19 22:04 ` Daniel Lezcano
2017-10-19 22:25 ` Thomas Gleixner
2017-10-20 6:46 ` Daniel Lezcano
2017-10-20 7:49 ` David Kozub
2017-10-20 9:35 ` Daniel Lezcano
2017-10-20 9:40 ` Thomas Gleixner
2017-10-20 9:46 ` Daniel Lezcano
2017-10-20 14:59 ` David Kozub
2017-10-19 22:21 ` Thomas Gleixner
2017-10-20 7:38 ` David Kozub [this message]
2017-10-20 8:18 ` Thomas Gleixner
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.LRH.2.21.1710200930370.3927@linux.fjfi.cvut.cz \
--to=zub@linux.fjfi.cvut.cz \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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®