linux-kernel - Re: [PATCH 0/2] Revert patches fixing probing of interrupts

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]

Date:   Sun, 1 Dec 2019 18:54:45 -0500
From:   Stefan Berger <stefanb@...ux.ibm.com>
To:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Stefan Berger <stefanb@...ux.vnet.ibm.com>
Cc:     linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH 0/2] Revert patches fixing probing of interrupts

On 11/29/19 5:37 PM, Jarkko Sakkinen wrote:
> On Tue, Nov 26, 2019 at 08:17:51AM -0500, Stefan Berger wrote:
>> From: Stefan Berger <stefanb@...ux.ibm.com>
>>
>> Revert the patches that were fixing the probing of interrupts due
>> to reports of interrupt stroms on some systems
> Can you explain how reverting is going to fix the issue?


The reverts fix 'the interrupt storm issue' that they are causing on 
some systems but don't fix the issue with the interrupt mode not being 
used. I was hoping Jerry would get access to a system faster but this 
didn't seem to be the case. So sending these patches seemed the better 
solution than leaving 5.4.x with the problem but going back to when it 
worked 'better.'


>
> This is wrong way to move forward. The root cause must be identified
> first and then decide actions like always in any situation.
>
> /Jarkko