linux-kernel - Re: [PATCH] pci-sysfs: Make PCI bridge attribute visible in sysfs

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] [day] [month] [year] [list]

Date:   Thu, 4 May 2017 07:58:44 -0500
From:   Bjorn Helgaas <bhelgaas@...gle.com>
To:     Vee Khee Wong <vee.khee.wong@...com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Jonathan Hearn <jonathan.hearn@...com>,
        "Ram.Amrani@...ium.com" <Ram.Amrani@...ium.com>,
        Hui Chun Ong <hui.chun.ong@...com>,
        "shhuiw@...mail.com" <shhuiw@...mail.com>,
        "rajatja@...gle.com" <rajatja@...gle.com>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "keith.busch@...el.com" <keith.busch@...el.com>,
        "jonathan.yong@...el.com" <jonathan.yong@...el.com>
Subject: Re: [PATCH] pci-sysfs: Make PCI bridge attribute visible in sysfs

On Thu, May 4, 2017 at 2:32 AM, Vee Khee Wong <vee.khee.wong@...com> wrote:
>
>
> On Mon, 2017-04-17 at 10:41 -0500, Bjorn Helgaas wrote:
>> On Mon, Apr 17, 2017 at 12:50 AM, Wong Vee Khee <vee.khee.wong@...com
>> > wrote:
>> >
>> > From: vwong <vee.khee.wong@...com>
>> >
>> > Export the PCIe link attributes of PCI bridges to sysfs.
>> This needs justification for *why* we should export these via sysfs.
>>
>> Some of these things, e.g., secondary/subordinate bus numbers, are
>> already visible to non-privileged users via "lspci -v".
>>
> We need to expose these attributes via sysfs due to several reasons
> listed below:
>
> 1) PCIe capabilities info such as Maximum/Actual link width and link speed only visible to privileged users via "lspci -vvv". The software that my team is working on need to get PCIe link information as non-root user.
>
> 2) From a client perspective, it require a lot of overhead parsing output of lspci to get PCIe capabilities. Our application is only interested in getting PCIe bridges but lspci print info for all PCIe devices.

I'm looking for a revised patch that incorporates the justification in
the changelog and addresses the code comments I made.

Bjorn