linux-kernel - Re: [patch part-II V2 07/13] x86/entry: Move irq tracing on syscall entry to C-code

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 13 Mar 2020 16:16:19 +0100
From:   Frederic Weisbecker <frederic@...nel.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
        Steven Rostedt <rostedt@...dmis.org>,
        Brian Gerst <brgerst@...il.com>,
        Juergen Gross <jgross@...e.com>,
        Alexandre Chartre <alexandre.chartre@...cle.com>
Subject: Re: [patch part-II V2 07/13] x86/entry: Move irq tracing on syscall
 entry to C-code

On Sun, Mar 08, 2020 at 11:24:06PM +0100, Thomas Gleixner wrote:
> Now that the C entry points are safe, move the irq flags tracing code into
> the entry helper.
>

The consolidation is most welcome but the changelog is still a bit
misleading. The fact that the C entry points are now safe doesn't
make irq flags tracing safe itself.

Thanks.

> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> Reviewed-by: Frederic Weisbecker <frederic@...nel.org>
> Reviewed-by: Alexandre Chartre <alexandre.chartre@...cle.com>