linux-kernel - Re: [PATCH v10 3/4] PCI/DOE: Expose the DOE features 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]

Date: Sat, 15 Jun 2024 15:12:55 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc: Alistair Francis <alistair23@...il.com>, bhelgaas@...gle.com,
	linux-pci@...r.kernel.org, alex.williamson@...hat.com,
	christian.koenig@....com, kch@...dia.com,
	gregkh@...uxfoundation.org, logang@...tatee.com,
	linux-kernel@...r.kernel.org, chaitanyak@...dia.com,
	rdunlap@...radead.org, Alistair Francis <alistair.francis@....com>
Subject: Re: [PATCH v10 3/4] PCI/DOE: Expose the DOE features via sysfs

On Thu, May 23, 2024 at 12:24:48PM +0100, Jonathan Cameron wrote:
> What happens if multiple DOE which support the same protocol?
> (IIRC that's allowed).  You probably need to paper over repeat
> sysfs attributes and make sure they don't get double freed etc.

So I believe this was fixed in v11 but assuming the point here is
to allow lspci to display supported protocols without speaking DOE
with the device, the way it's implemented now user space cannot
discern which mailbox supports which protocol.  Or if multiple
mailboxes support the same protocol.  I'm wondering in how far
that limits the usefulness of the feature.

sysfs doesn't support nested groups.  But we could dynamically
create one attribute group per mailbox.  Or have one file per
mailbox in a common doe_features group, each file containing
all the supported protocols. Hm...

Thanks,

Lukas