linux-kernel - Re: [PATCH v2 06/11] smp: use smp_call_private() fron irq

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: <20220425093737.GH2731@worktop.programming.kicks-ass.net>
Date:   Mon, 25 Apr 2022 11:37:37 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Donghai Qiao <dqiao@...hat.com>
Cc:     akpm@...ux-foundation.org, sfr@...b.auug.org.au, arnd@...db.de,
        heying24@...wei.com, andriy.shevchenko@...ux.intel.com,
        axboe@...nel.dk, rdunlap@...radead.org, tglx@...utronix.de,
        gor@...ux.ibm.com, donghai.w.qiao@...il.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 06/11] smp: use smp_call_private() fron irq_work.c and
 core.c

On Fri, Apr 22, 2022 at 04:00:35PM -0400, Donghai Qiao wrote:
> irq_work.c and core.c should use the cross interface rather than
> using a unpublished internal function __smp_call_single_queue.

They should do no such thing, using an unpublished/private interface was
on purpose. Nobody else should be able to do these things.