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]

Message-ID: <20150302172108.GN17694@htj.duckdns.org>
Date:	Mon, 2 Mar 2015 12:21:08 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Alexander Gordeev <agordeev@...hat.com>
Cc:	Stefan Bader <stefan.bader@...onical.com>,
	Sander Eikelenboom <linux@...elenboom.it>,
	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 Mon, Feb 16, 2015 at 05:28:42PM +0000, Alexander Gordeev wrote:
> The problem dates back to commit 4f37b50 ("libata: Use dev_name() for
> request_irq() to distinguish devices"). If the commit is considered valid
> then <BDF> still might be legitimate as well. Not sure what is the best
> approach here.

What does <BDF> indicate?  Does it successfully identify the device in
question?

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/