bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sami Tolvanen <samitolvanen@google.com>,
	Kees Cook <keescook@chromium.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Will Deacon <will@kernel.org>, Jessica Yu <jeyu@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Tejun Heo <tj@kernel.org>,
	Christoph Hellwig <hch@infradead.org>, bpf <bpf@vger.kernel.org>,
	linux-hardening@vger.kernel.org,
	linux-arch <linux-arch@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	PCI <linux-pci@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 01/17] add support for Clang CFI
Date: Fri, 19 Mar 2021 06:52:29 -0700	[thread overview]
Message-ID: <20210319135229.GJ2696@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <YFSYkyNFb34N8Ile@hirez.programming.kicks-ass.net>

On Fri, Mar 19, 2021 at 01:26:59PM +0100, Peter Zijlstra wrote:
> On Thu, Mar 18, 2021 at 04:48:43PM -0700, Sami Tolvanen wrote:
> > On Thu, Mar 18, 2021 at 3:29 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > On Thu, Mar 18, 2021 at 10:10:55AM -0700, Sami Tolvanen wrote:
> > > > +static void update_shadow(struct module *mod, unsigned long base_addr,
> > > > +             update_shadow_fn fn)
> > > > +{
> > > > +     struct cfi_shadow *prev;
> > > > +     struct cfi_shadow *next;
> > > > +     unsigned long min_addr, max_addr;
> > > > +
> > > > +     next = vmalloc(SHADOW_SIZE);
> > > > +
> > > > +     mutex_lock(&shadow_update_lock);
> > > > +     prev = rcu_dereference_protected(cfi_shadow,
> > > > +                                      mutex_is_locked(&shadow_update_lock));
> > > > +
> > > > +     if (next) {
> > > > +             next->base = base_addr >> PAGE_SHIFT;
> > > > +             prepare_next_shadow(prev, next);
> > > > +
> > > > +             min_addr = (unsigned long)mod->core_layout.base;
> > > > +             max_addr = min_addr + mod->core_layout.text_size;
> > > > +             fn(next, mod, min_addr & PAGE_MASK, max_addr & PAGE_MASK);
> > > > +
> > > > +             set_memory_ro((unsigned long)next, SHADOW_PAGES);
> > > > +     }
> > > > +
> > > > +     rcu_assign_pointer(cfi_shadow, next);
> > > > +     mutex_unlock(&shadow_update_lock);
> > > > +     synchronize_rcu_expedited();
> > >
> > > expedited is BAD(tm), why is it required and why doesn't it have a
> > > comment?
> > 
> > Ah, this uses synchronize_rcu_expedited() because we have a case where
> > synchronize_rcu() hangs here with a specific SoC family after the
> > vendor's cpu_pm driver powers down CPU cores.
> 
> Broken vendor drivers seem like an exceedingly poor reason for this.

The vendor is supposed to make sure that RCU sees the CPU cores as either
deep idle or offline before powering them down.  My guess is that the
CPU is powered down, but RCU (and probably much else in the system)
thinks that the CPU is still up and running.  So I bet that you are
seeing other issues as well.

I take it that the IPIs from synchronize_rcu_expedited() have the effect
of momentarily powering up those CPUs?

							Thanx, Paul

  reply	other threads:[~2021-03-19 13:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 17:10 [PATCH v2 00/17] Add support for Clang CFI Sami Tolvanen
2021-03-18 17:10 ` [PATCH v2 01/17] add " Sami Tolvanen
2021-03-18 22:29   ` Peter Zijlstra
2021-03-18 23:48     ` Sami Tolvanen
2021-03-19 12:26       ` Peter Zijlstra
2021-03-19 13:52         ` Paul E. McKenney [this message]
2021-03-19 16:17           ` Sami Tolvanen
2021-03-19 17:03             ` Paul E. McKenney
2021-03-18 17:10 ` [PATCH v2 02/17] cfi: add __cficanonical Sami Tolvanen
2021-03-18 17:49   ` Nick Desaulniers
2021-03-18 17:10 ` [PATCH v2 03/17] mm: add generic __va_function and __pa_function macros Sami Tolvanen
2021-03-18 17:10 ` [PATCH v2 04/17] module: ensure __cfi_check alignment Sami Tolvanen
2021-03-18 19:27   ` Nick Desaulniers
2021-03-18 21:43     ` Sami Tolvanen
2021-03-18 17:10 ` [PATCH v2 05/17] workqueue: use WARN_ON_FUNCTION_MISMATCH Sami Tolvanen
2021-03-18 18:50   ` Nick Desaulniers
2021-03-18 21:38     ` Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 06/17] kthread: " Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 07/17] kallsyms: strip ThinLTO hashes from static functions Sami Tolvanen
2021-03-18 19:00   ` Nick Desaulniers
2021-03-18 21:41     ` Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 08/17] bpf: disable CFI in dispatcher functions Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 09/17] lib/list_sort: fix function type mismatches Sami Tolvanen
2021-03-18 18:31   ` Nick Desaulniers
2021-03-18 21:31     ` Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 10/17] lkdtm: use __va_function Sami Tolvanen
2021-03-18 18:43   ` Nick Desaulniers
2021-03-18 18:45     ` Nick Desaulniers
2021-03-18 17:11 ` [PATCH v2 11/17] psci: use __pa_function for cpu_resume Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 12/17] arm64: implement __va_function Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 13/17] arm64: use __pa_function Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 14/17] arm64: add __nocfi to functions that jump to a physical address Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 15/17] arm64: add __nocfi to __apply_alternatives Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 16/17] KVM: arm64: Disable CFI for nVHE Sami Tolvanen
2021-03-18 17:11 ` [PATCH v2 17/17] arm64: allow CONFIG_CFI_CLANG to be selected Sami Tolvanen

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=20210319135229.GJ2696@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bpf@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=jeyu@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=samitolvanen@google.com \
    --cc=tj@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).