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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <87zhcjdeu2.fsf@nanos.tec.linutronix.de>
Date:   Sat, 14 Mar 2020 00:17:57 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Frederic Weisbecker <frederic@...nel.org>
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

Frederic Weisbecker <frederic@...nel.org> writes:

> 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.

Yes, that comes in a later patch. Bah. And of course I'm reworking this
ATM with the new section magic and analyzing the fallout with help of
the objtool extension Peter did for this.

Still writing changelogs and trying to make sense of things we find that
way.

Thanks,

        tglx