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: <20151204081350.2113b7e6@why.wild-wind.fr.eu.org>
Date:	Fri, 4 Dec 2015 08:13:50 +0000
From:	Marc Zyngier <marc.zyngier@....com>
To:	Bjorn Helgaas <helgaas@...nel.org>
Cc:	Phil Edworthy <phil.edworthy@...esas.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jiang Liu <jiang.liu@...ux.intel.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Wolfram Sang <wsa@...-dreams.de>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH] PCI: MSI: Only use the generic MSI layer when domain is
 hierarchical

On Thu, 3 Dec 2015 18:27:59 -0600
Bjorn Helgaas <helgaas@...nel.org> wrote:

> On Mon, Nov 30, 2015 at 10:25:34AM +0000, Phil Edworthy wrote:
> > Cc'd linux-pci ml
> > 
> > On 23 November 2015 14:27, Marc Zyngier wrote:
> > 
> > Since d8a1cb757550 ("PCI/MSI: Let pci_msi_get_domain use struct
> > device::msi_domain"), we use the MSI domain associated to the PCI device.
> > 
> > But finding a MSI domain doesn't mean that the domain is implemented
> > using the generic MSI domain API, and a number of MSI controllers
> > are still using the arch_setup_msi_irq/arch_teardown_msi_irqs.
> > 
> > In order to avoid a firework on these systems, check that the domain
> > we just obtained is hierarchical. If not, don't use the generic MSI
> > stuff and stick with the old one. Not pretty, but reliable.
> > 
> > Another insentive to rework those drivers and phase out this API.
> > 
> > Reported-by: Phil Edworthy <phil.edworthy@...esas.com>
> > Tested-by: Phil Edworthy <phil.edworthy@...esas.com>
> > Signed-off-by: Marc Zyngier <marc.zyngier@....com>
> 
> Thanks, I applied this with Thomas' ack to pci/msi for v4.5.
> 
> It looks like d8a1cb757550 appeared in v4.3.  Is this a fix for that
> commit?  Does this need to be backported via a stable tag?

Hi Bjorn,

I think this really deserves to be queued as an immediate fix for 4.4
rather than 4.5, as some systems in mainline are affected by this bug:

http://www.spinics.net/lists/arm-kernel/msg465792.html

It would also deserve a stable tag for 4.3.

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ