public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: "Krzysztof Wilczy´nski" <kw@linux.com>
Cc: "Matthew Wood" <thepacketgeek@gmail.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Mario Limonciello" <superm1@kernel.org>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [RESEND PATCH v7 1/1] PCI/sysfs: Expose PCIe device serial number
Date: Mon, 15 Sep 2025 08:28:56 -0600	[thread overview]
Message-ID: <aMgiqJVWTptU6Fq0@kbusch-mbp> (raw)
In-Reply-To: <20250913061720.GA1992308@rocinante>

On Sat, Sep 13, 2025 at 03:17:20PM +0900, Krzysztof Wilczy´nski wrote:
> Who needs this?  Why is this useful?  Why hasn't there been a need for
> exposing serial number in past decades,

I can't speak for other reviewers for their interest in having such an
attribute. Matt provided the reasoning here in the cover letter by
making it possible to access from unpriviledged applications that are
managing devices assigned to them without jumping through hoops to get
that information.

> and suddenly we need it so desperately?

"desperately" is a bit of a stretch. This simple patch has been out for
many months now, missed 2 merge windows with zero negative feedback, and
we're about to miss a 3rd. At this point, "frustration" would be a
better description.
 
> We probably wouldn't want to add this if there is only a single user that
> needs this, 

There's multiple reviewers representing different companies.

> especially give that userspace tools like lspci already expose
> this when someone needs it.

Only if you're root. This new attribute is admin-only by default too,
but can be changed as needed.

> Also, we were reluctant to expose some types of information, like serial
> numbers and such, via the VPD recently, so why exposing any serial numbers
> via sysfs would be any different?

It's a specification defined attribute of a device, and sysfs is the
interface that exports device attributes.

  parent reply	other threads:[~2025-09-15 14:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 23:22 [RESEND PATCH v7 0/1] PCI/sysfs: Expose PCIe device serial number Matthew Wood
2025-08-21 23:22 ` [RESEND PATCH v7 1/1] " Matthew Wood
2025-08-22  0:04   ` Keith Busch
2025-08-27  1:34   ` Hans Zhang
2025-08-27 19:39   ` Keith Busch
2025-09-12 16:56     ` Keith Busch
2025-09-13  6:17     ` Krzysztof Wilczyński
2025-09-15 10:03       ` Jonathan Cameron
2025-09-15 14:28       ` Keith Busch [this message]
2025-09-13  6:20   ` Krzysztof Wilczyński
2025-09-15 22:23     ` Keith Busch
2025-09-16 13:53       ` Jonathan Cameron
2025-09-15 19:39   ` Bjorn Helgaas
2025-09-16 22:35     ` Keith Busch
2025-09-17  8:34       ` Krzysztof Wilczyński
2025-09-17  8:52         ` Thomas Weißschuh
2025-09-17 12:16           ` Krzysztof Wilczyński
2025-09-17  9:08         ` Matthew Wood
2025-09-17 12:17           ` Krzysztof Wilczyński
2025-09-17  8:36     ` Krzysztof Wilczyński
  -- strict thread matches above, loose matches on Subject: below --
2025-08-11 17:39 [RESEND PATCH v7 0/1] " Matthew Wood
2025-08-11 17:39 ` [RESEND PATCH v7 1/1] " Matthew Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aMgiqJVWTptU6Fq0@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=superm1@kernel.org \
    --cc=thepacketgeek@gmail.com \
    --cc=thomas.weissschuh@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox