linux-kernel - Re: [PATCH] x86/apic/msi: check interupt context before reporting warning

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: <874kcychz5.ffs@nanos.tec.linutronix.de>
Date:   Tue, 13 Jul 2021 18:10:38 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Yongxin Liu <yongxin.liu@...driver.com>
Cc:     evgreen@...omium.org, rajatja@...gle.com, bhelgaas@...gle.com,
        stable@...r.kernel.org, linux-pci@...r.kernel.org, x86@...nel.org,
        maz@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/apic/msi: check interupt context before reporting warning

On Tue, Jul 13 2021 at 14:46, Yongxin Liu wrote:
> Affinity change can happen in both interrupt context and non-interrupt
> context. The paranoia check for interrupt target cpu is not always true
> in non-interrupt context.

Supressing the warning is just papering over a larger underlying problem
which was discussed recently already. I'm working on a fix for that
already.

Thanks,

        tglx