linux-kernel - Re: [PATCH] smp: generic ipi

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: <a9fbbf7d-28cd-2119-8519-2f1cd045acda@gmail.com>
Date:   Wed, 20 May 2020 14:42:10 +0100
From:   Wojciech Kudla <wk.kernel@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Nadav Amit <namit@...are.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] smp: generic ipi_raise tracepoint

On 20/05/2020 14:33, Peter Zijlstra wrote:
> We have bright shiny links like: https://lkml.kernel.org/r/$MSG-ID for
> that. they allow me to go find the email in my local archive without
> having to use a browser.

Apologies, beginner's mistake.

>> +static const char *ipi_reason_missing __tracepoint_string = "";
> 
> That is a pretty crap reason ;-)
> 

I knew this was a long shot. There is no obvious way to 
get/infer ipi reason in generic smp code at the moment.
Any suggestions what we can put here in the meantime?
Would "none" be more appropriate?