linux-kernel - Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in mainline kernel

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1516816150.4109.2.camel@redhat.com>
Date:   Wed, 24 Jan 2018 12:49:10 -0500
From:   Lyude Paul <lyude@...hat.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     hpa@...or.com, keith.busch@...el.com, mingo@...nel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: "irq/matrix: Spread interrupts on allocation" breaks nouveau in
 mainline kernel

Hi, please ignore the warning: it happens before and after the regressing
commit (I didn't actually mean to include it on the log I gave here, whoops).
As for how I determined nouveau is getting assigned the same IRQ vector as
another device, I checked using /sys/kernel/debug/irq. Additionally; when
nouveau does initialize properly after resume (e.g. after reverting this
patch) I see it get assigned a seperate vector from the other devices.

On Wed, 2018-01-24 at 13:52 +0100, Thomas Gleixner wrote:
> On Tue, 23 Jan 2018, Lyude Paul wrote:
> 
> > JFYI: I confirmed this patch is definitely broken. I'm seeing nouveau get
> > assigned the same MSI vector as another device on the system, which would
> > explain why interrupts suddenly stop working. I'll keep looking into it
> > further
> > tomorrow.
> 
> How did you determine that it is the same MSI vector as another device?
> 
> Thanks,
> 
> 	tglx
> 
-- 
Cheers,
	Lyude Paul