From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>,
paulmck@kernel.org, sfr@canb.auug.org.au
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: Re: [PATCH 2/3] rcu: Fix rcu_dynticks_curr_cpu_in_eqs() vs noinstr
Date: Wed, 29 Sep 2021 00:35:54 +0200 [thread overview]
Message-ID: <87bl4c9vlh.ffs@tglx> (raw)
In-Reply-To: <20210928084217.987503713@infradead.org>
On Tue, Sep 28 2021 at 10:40, Peter Zijlstra wrote:
> vmlinux.o: warning: objtool: rcu_nmi_enter()+0x36: call to __kasan_check_read() leaves .noinstr.text section
>
> noinstr cannot have atomic_*() functions in because they're explicitly
> annotated, use arch_atomic_*().
>
> Fixes: 2be57f732889 ("rcu: Weaken ->dynticks accesses and updates")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2021-09-28 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 8:40 [PATCH 0/3] rcu,sched: noinstr fixes Peter Zijlstra
2021-09-28 8:40 ` [PATCH 1/3] rcu: Always inline rcu_dynticks_task*_{enter,exit}() Peter Zijlstra
2021-09-28 22:35 ` Thomas Gleixner
2021-09-28 23:03 ` Paul E. McKenney
2021-09-28 8:40 ` [PATCH 2/3] rcu: Fix rcu_dynticks_curr_cpu_in_eqs() vs noinstr Peter Zijlstra
2021-09-28 22:35 ` Thomas Gleixner [this message]
2021-09-28 8:40 ` [PATCH 3/3] sched: Always inline is_percpu_thread() Peter Zijlstra
2021-09-28 22:36 ` Thomas Gleixner
2021-10-01 12:10 ` [tip: sched/urgent] " tip-bot2 for Peter Zijlstra
2021-09-28 18:15 ` [PATCH 0/3] rcu,sched: noinstr fixes Paul E. McKenney
2021-09-29 8:39 ` Peter Zijlstra
2021-09-29 15:29 ` Paul E. McKenney
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=87bl4c9vlh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.