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: <DM5PR12MB19161E66F534B7050B8CCBF0F8E20@DM5PR12MB1916.namprd12.prod.outlook.com>
Date:   Wed, 24 Jan 2018 19:13:09 +0000
From:   "Ghannam, Yazen" <Yazen.Ghannam@....com>
To:     Lyude Paul <lyude@...hat.com>, Thomas Gleixner <tglx@...utronix.de>
CC:     "hpa@...or.com" <hpa@...or.com>,
        "keith.busch@...el.com" <keith.busch@...el.com>,
        "mingo@...nel.org" <mingo@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Borislav Petkov" <bp@...en8.de>
Subject: RE: "irq/matrix: Spread interrupts on allocation" breaks nouveau in
 mainline kernel

> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org [mailto:linux-kernel-
> owner@...r.kernel.org] On Behalf Of Lyude Paul
> Sent: Wednesday, January 24, 2018 12:49 PM
> To: Thomas Gleixner <tglx@...utronix.de>
> Cc: hpa@...or.com; keith.busch@...el.com; mingo@...nel.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.
> 

+Boris. This thread seems to have split.

Lyude,
Does the warning show on mainline or does it only show when bisecting?

Sorry, I'm not sure what you mean by "it happens before and after the
regressing commit".


Boris,
In any case, I like your idea on saving the block addresses. I can look into this.

Thanks,
Yazen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ