linux-kernel - Re: [PATCH v3] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2023081224-famished-devotion-6e0e@gregkh>
Date:   Sat, 12 Aug 2023 10:26:32 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Lukas Wunner <lukas@...ner.de>
Cc:     Alistair Francis <alistair23@...il.com>, bhelgaas@...gle.com,
        linux-pci@...r.kernel.org, Jonathan.Cameron@...wei.com,
        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 v3] PCI/DOE: Expose the DOE protocols via sysfs

On Sat, Aug 12, 2023 at 10:15:26AM +0200, Lukas Wunner wrote:
> On Thu, Aug 10, 2023 at 11:34:11AM -0400, Alistair Francis wrote:
> > On Thu, Aug 10, 2023 at 3:34???AM Lukas Wunner <lukas@...ner.de> wrote:
> > > On Wed, Aug 09, 2023 at 07:28:51PM -0400, Alistair Francis wrote:
> > > > --- a/drivers/pci/pci-sysfs.c
> > > > +++ b/drivers/pci/pci-sysfs.c
> > > > @@ -1226,6 +1227,12 @@ static int pci_create_resource_files(struct pci_dev *pdev)
> > > >       int i;
> > > >       int retval;
> > > >
> > > > +#ifdef CONFIG_PCI_DOE
> > > > +     retval = doe_sysfs_init(pdev);
> > > > +     if (retval)
> > > > +             return retval;
> > > > +#endif
> > > > +
> > >
> > > The preferred way to expose PCI sysfs attributes nowadays is to add them
> > > to pci_dev_attr_groups[] and use the ->is_visible callback to check
> > > whether they're applicable to a particular pci_dev.  The alternative
> > > via pci_create_resource_files() has race conditions which I think
> > > still haven't been fixed. Bjorn recommended the ->is_visible approach
> > > in response to the most recent attempt to fix the race:
> > >
> > > https://lore.kernel.org/linux-pci/20230427161458.GA249886@bhelgaas/
> > 
> > The is_visible doen't seem to work in this case.
> > 
> > AFAIK is_visible only applies to the attributes under the group. Which
> > means that every PCIe device will see a `doe_protos` directory, no
> > matter if DOE is supported.
> 
> internal_create_group() in fs/sysfs/group.c does this:
> 
> 	if (grp->name) {
> 			...
> 			kn = kernfs_create_dir_ns(kobj->sd, grp->name, ...
> 
> So I'm under the impression that if you set the ->name member of
> struct attribute_group, the attributes in that group appear under
> a directory of that name.
> 
> In fact, the kernel-doc for struct attribute_group claims as much:
> 
>  * struct attribute_group - data structure used to declare an attribute group.
>  * @name:	Optional: Attribute group name
>  *		If specified, the attribute group will be created in
>  *		a new subdirectory with this name.
> 
> So I don't quite understand why you think that "every PCIe device will
> see a `doe_protos` directory, no matter if DOE is supported"?
> 
> Am I missing something?

I think the issue might be that the directory will be created even if no
attributes are present in it due to the is_visable() check not returning
any valid files?

If so, I had a patch somewhere around here where I was trying to fix
that up:
	https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?h=debugfs_cleanup&id=f670945dfbaf353fe068544c31e3fa45575da5b5
but it didn't seem to work properly and kept crashing.  I didn't spend
much time on looking into it, but if this is an issue, I can work on
fixing this properly.

thanks,

greg k-h