linux-kernel - Re: [PATCH v2] PCI/DOE: Expose the DOE protocols via 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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2023080553-daringly-raider-0135@gregkh>
Date:   Sat, 5 Aug 2023 07:59:51 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Lukas Wunner <lukas@...ner.de>
Cc:     Alistair Francis <alistair23@...il.com>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        bhelgaas@...gle.com, linux-pci@...r.kernel.org,
        alex.williamson@...hat.com, christian.koenig@....com,
        kch@...dia.com, logang@...tatee.com, linux-kernel@...r.kernel.org,
        Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH v2] PCI/DOE: Expose the DOE protocols via sysfs

On Fri, Aug 04, 2023 at 06:05:42PM +0200, Lukas Wunner wrote:
> On Fri, Aug 04, 2023 at 11:17:59AM -0400, Alistair Francis wrote:
> > On Wed, Aug 2, 2023 at 6:52???PM Lukas Wunner <lukas@...ner.de> wrote:
> > > I kind of like the approach of exposing a list which can be grep'ed,
> > > even though it may go against the rule of having just one datum per
> > > attribute.  I'd prefer a representation that's human-readable though,
> > > e.g. "0001:01" for CMA-SPDM.
> > 
> > Yeah, it's my preferred method as well, but it's not going to be
> > accepted upstream
> 
> How about procfs instead of sysfs?

No, procfs is for "processes", not devices.

> No "single datum per file" rule over there.
> PCI content goes into /proc/bus/pci/.
> Already used by lspci to access config space.

And that is old legacy stuff, please, let us learn from our past
mistakes in api creation, sysfs was created this way for a reason (i.e.
large files in procfs do not work well over time.)

thanks,

greg k-h