linux-kernel - Re: [PATCH] bus: omap_l3_noc: mark l3 irqs as IRQF_NO

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

Message-ID: <YBubhS4NprkdPcDM@atomide.com>
Date:   Thu, 4 Feb 2021 09:00:21 +0200
From:   Tony Lindgren <tony@...mide.com>
To:     Grygorii Strashko <grygorii.strashko@...com>
Cc:     Lokesh Vutla <lokeshvutla@...com>, Nishanth Menon <nm@...com>,
        linux-kernel@...r.kernel.org,
        Carl-Oscar Varnander 
        <carl-oscar.varnander@...achi-powergrids.com>,
        linux-omap@...r.kernel.org
Subject: Re: [PATCH] bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD

* Grygorii Strashko <grygorii.strashko@...com> [210128 21:16]:
> The main purpose of l3 IRQs is to catch OCP bus access errors and identify
> corresponding code places by showing call stack, so it's important to
> handle L3 interconnect errors as fast as possible. On RT these IRQs will
> became threaded and will be scheduled mach more late from the moment actual
> error occurred so showing completely useless information.
> 
> Hence, mark l3 IRQs as IRQF_NO_THREAD so they will not be forced threaded
> on RT or if force_irqthreads = true.
> 
> Fixes: 0ee7261c9212 ("drivers: bus: Move the OMAP interconnect driver to drivers/bus/")

Thanks applying into fixes.

Tony