From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Crispin <john@phrozen.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH stable] tick/nohz: Prevent bogus softirq pending warning
Date: Thu, 30 Aug 2018 17:12:54 +0200 [thread overview]
Message-ID: <20180830151253.GB27947@lerouge> (raw)
In-Reply-To: <alpine.DEB.2.21.1808301702450.1210@nanos.tec.linutronix.de>
On Thu, Aug 30, 2018 at 05:05:19PM +0200, Thomas Gleixner wrote:
> Commit 0a0e0829f990 ("nohz: Fix missing tick reprogram when interrupting an
> inline softirq") got backported to stable trees and now causes the NOHZ
> softirq pending warning to trigger. It's not an upstream issue as the NOHZ
> update logic has been changed there.
>
> The problem is when a softirq disabled section gets interrupted and on
> return from interrupt the tick/nohz state is evaluated, which then can
> observe pending soft interrupts. These soft interrupts are legitimately
> pending because they cannot be processed as long as soft interrupts are
> disabled and the interrupted code will correctly process them when soft
> interrupts are reenabled.
>
> Add a check for softirqs disabled to the pending check to prevent the
> warning.
>
> Reported-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Reported-by: John Crispin <john@phrozen.org>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Tested-by: John Crispin <john@phrozen.org>
Acked-by: Frederic Weisbecker <frederic@kernel.org>
Thanks for cooking the patch!
next prev parent reply other threads:[~2018-08-30 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 15:05 [PATCH stable] tick/nohz: Prevent bogus softirq pending warning Thomas Gleixner
2018-08-30 15:12 ` Frederic Weisbecker [this message]
2018-09-12 13:56 ` Geert Uytterhoeven
2018-09-27 8:07 ` Geert Uytterhoeven
2018-09-27 8:48 ` Greg KH
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=20180830151253.GB27947@lerouge \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).