linux-kernel - Re: 3.19: device name associates with IRQ's for ahci controllers operating with a single IRQ changed from "ahci?" to "<BDF>"

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:	Tue, 10 Feb 2015 09:51:20 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Stefan Bader <stefan.bader@...onical.com>
Cc:	Sander Eikelenboom <linux@...elenboom.it>,
	Alexander Gordeev <agordeev@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.19: device name associates with IRQ's for ahci controllers
 operating with a single IRQ changed from "ahci?" to "<BDF>"

Hello,

On Tue, Feb 10, 2015 at 08:57:46AM +0100, Stefan Bader wrote:
> On 09.02.2015 20:54, Sander Eikelenboom wrote:
> > Hi.
> > 
> > In 3.19 the device name associates with IRQ's for ahci controllers operating
> > with a single IRQ changed from "ahci?" to "<BDF>", was this intentional ?
> > 
> > It's probably commit 18dcf433f3ded61eb140a55e7048ec2fef79e723 (or another one
> > in that series). 
> 
> Oh, looking at that commit that might make sense. In
> ahci_host_activate_single_irq it now uses dev_driver_name instead of dev_name as
> it did before (from ata_host_activate).  The description sounds like before the
> driver is registered this will return the bus. And registering an interrupt
> would likely be before the driver is fully registered... But you probably saw
> that, too. Whether that really was intentional is still the question. :)

Urgh... Alexander, can you please send a patch to fix up the names?

Thanks.

-- 
tejun
--
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/