public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jiafei Pan <Jiafei.Pan@nxp.com>
Cc: mingo@kernel.org, tglx@linutronix.de, rostedt@goodmis.org,
	romain.perier@gmail.com, will@kernel.org,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	leoyang.li@nxp.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH] softirq: add irq off checking for __raise_softirq_irqoff
Date: Thu, 13 Aug 2020 07:58:22 +0200	[thread overview]
Message-ID: <20200813055822.GC3982@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20200806040729.39186-1-Jiafei.Pan@nxp.com>

On Thu, Aug 06, 2020 at 12:07:29PM +0800, Jiafei Pan wrote:
> __raise_softirq_irqoff will update per-CPU mask of pending softirqs,
> it need to be called in irq disabled context in order to keep it atomic
> operation, otherwise it will be interrupted by hardware interrupt,
> and per-CPU softirqs pending mask will be corrupted, the result is
> there will be unexpected issue, for example hrtimer soft irq will
> be losed and soft hrtimer will never be expire and handled.
> 
> Adding irqs disabled checking here to provide warning in irqs enabled
> context.
> 
> Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
> ---
>  kernel/softirq.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/kernel/softirq.c b/kernel/softirq.c
> index bf88d7f62433..11f61e54a3ae 100644
> --- a/kernel/softirq.c
> +++ b/kernel/softirq.c
> @@ -481,6 +481,11 @@ void raise_softirq(unsigned int nr)
>  
>  void __raise_softirq_irqoff(unsigned int nr)
>  {
> +	/* This function can only be called in irq disabled context,
> +	 * otherwise or_softirq_pending will be interrupted by hardware
> +	 * interrupt, so that there will be unexpected issue.
> +	 */

Comment style is wrong, also I'm not sure the comment is really
helpfull.

> +	WARN_ON_ONCE(!irqs_disabled());

	lockdep_assert_irqs_disabled();

>  	trace_softirq_raise(nr);
>  	or_softirq_pending(1UL << nr);
>  }

  parent reply	other threads:[~2020-08-13  5:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  4:07 [PATCH] softirq: add irq off checking for __raise_softirq_irqoff Jiafei Pan
2020-08-13  3:03 ` Jiafei Pan
2020-08-13 14:56   ` Steven Rostedt
2020-08-14  2:21     ` [EXT] " Jiafei Pan
2020-08-14  2:24       ` Steven Rostedt
2020-08-14  4:17     ` Jiafei Pan
2020-08-13  5:58 ` Peter Zijlstra [this message]
2020-08-14  3:28   ` Jiafei Pan
2020-08-13  7:33 ` 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=20200813055822.GC3982@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Jiafei.Pan@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=romain.perier@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vladimir.oltean@nxp.com \
    --cc=will@kernel.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