linux-kernel - Re: [PATCH v2 2/2] tracing: Avoid isolated CPUs when queueing fsnotify irqwork

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] [day] [month] [year] [list]

Message-ID: <b823e468-3c98-44d8-ccf6-8a9ddc769fb5@redhat.com>
Date:   Tue, 1 Mar 2022 19:58:23 +0100
From:   Daniel Bristot de Oliveira <bristot@...hat.com>
To:     Nicolas Saenz Julienne <nsaenzju@...hat.com>, mingo@...hat.com,
        peterz@...radead.org, frederic@...nel.org, rostedt@...dmis.org
Cc:     tglx@...utronix.de, mtosatti@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] tracing: Avoid isolated CPUs when queueing
 fsnotify irqwork

On 3/1/22 12:30, Nicolas Saenz Julienne wrote:
> There isn't any need for this irq_work to be run locally, so avoid doing
> so when the CPU is isolated.
> 
> Note that this is especially bad as queueing it into a local isolated
> CPU might add noise to what was meant to be traced in the first place.
> 
> Signed-off-by: Nicolas Saenz Julienne <nsaenzju@...hat.com>

Reviewed-by: Daniel Bristot de Oliveira <bristot@...nel.org>

-- Daniel