lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 5 Oct 2021 16:20:37 +0200
From:   Peter Zijlstra <>
To:     Marco Elver <>
Cc:     "Paul E . McKenney" <>,
        Alexander Potapenko <>,
        Boqun Feng <>,
        Borislav Petkov <>,
        Dmitry Vyukov <>,
        Ingo Molnar <>,
        Josh Poimboeuf <>,
        Mark Rutland <>,
        Thomas Gleixner <>,
        Waiman Long <>,
        Will Deacon <>,,,,,,,
Subject: Re: [PATCH -rcu/kcsan 04/23] kcsan: Add core support for a subset of
 weak memory modeling

On Tue, Oct 05, 2021 at 03:13:25PM +0200, Marco Elver wrote:
> On Tue, 5 Oct 2021 at 14:53, Peter Zijlstra <> wrote:

> > And since you want to mark these functions as uaccess_safe, there must
> > not be any tracing on, hence notrace.
> In the Makefile we've relied on:
> just to disable it for all code here. That should be enough, right?

I find these implicit notrace thingies terribly confusing :/ I've
reported fail to rostedt a number of times only to be (re)told about
these Makefile level thingies.

Ideally we'd script notrace on every implicit symbol or something.

Powered by blists - more mailing lists