From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Matthew Wood <thepacketgeek@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Mario Limonciello <superm1@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v5 1/1] PCI/sysfs: Expose PCIe device serial number
Date: Mon, 21 Jul 2025 10:48:16 +0100 [thread overview]
Message-ID: <20250721104816.00003feb@huawei.com> (raw)
In-Reply-To: <20250718125935-75fa0343-af78-42be-bc3f-e8f806a4aee5@linutronix.de>
On Fri, 18 Jul 2025 13:02:00 +0200
Thomas Weißschuh <thomas.weissschuh@linutronix.de> wrote:
> On Fri, Jul 18, 2025 at 11:36:11AM +0100, Jonathan Cameron wrote:
> > On Thu, 17 Jul 2025 09:50:54 -0700
> > Matthew Wood <thepacketgeek@gmail.com> wrote:
>
> (...)
>
> > > diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c
> > > index 268c69daa4d5..bc0e0add15d1 100644
> > > --- a/drivers/pci/pci-sysfs.c
> > > +++ b/drivers/pci/pci-sysfs.c
> > > @@ -239,6 +239,22 @@ static ssize_t current_link_width_show(struct device *dev,
> > > }
> > > static DEVICE_ATTR_RO(current_link_width);
> > >
> > > +static ssize_t serial_number_show(struct device *dev,
> > > + struct device_attribute *attr, char *buf)
> > > +{
> > > + struct pci_dev *pci_dev = to_pci_dev(dev);
> > > + u64 dsn;
> > > +
> > > + dsn = pci_get_dsn(pci_dev);
> > > + if (!dsn)
> > > + return -EIO;
> > > +
> > > + return sysfs_emit(buf, "%02llx-%02llx-%02llx-%02llx-%02llx-%02llx-%02llx-%02llx\n",
> > > + dsn >> 56, (dsn >> 48) & 0xff, (dsn >> 40) & 0xff, (dsn >> 32) & 0xff,
> > > + (dsn >> 24) & 0xff, (dsn >> 16) & 0xff, (dsn >> 8) & 0xff, dsn & 0xff);
> >
> > I wonder if doing the following i too esoteric. Eyeballing those shifts is painful.
> >
> > u8 bytewise[8]; /* naming hard... */
> >
> > put_unaligned_u64(dsn, bytewise);
> >
> > return sysfs_emit(buf, "%02x-%02x-%02x-%02x-%02x-%02x-%02x-%02x\n",
> > bytewise[0], bytewise[1], bytewise[2], bytewise[3],
> > bytewise[4], bytewise[5], bytewise[6], bytewise[7]);
>
> This looks endianess-unsafe.
>
> Maybe just do what some drivers are doing:
>
> u8 bytes[8];
>
> put_unaligned_be64(dsn, bytes);
Absolutely. Typo :( I don't think there is a put_unaligned_u64()
>
> return sysfs_emit(buf, "%8phD");
>
> >
> >
> > > +}
> > > +static DEVICE_ATTR_ADMIN_RO(serial_number);
> >
> >
>
prev parent reply other threads:[~2025-07-21 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 16:50 [PATCH v5 0/1] PCI/sysfs: Expose PCIe device serial number Matthew Wood
2025-07-17 16:50 ` [PATCH v5 1/1] " Matthew Wood
2025-07-18 10:36 ` Jonathan Cameron
2025-07-18 11:02 ` Thomas Weißschuh
2025-07-18 16:27 ` Matthew Wood
2025-07-21 9:48 ` Jonathan Cameron [this message]
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=20250721104816.00003feb@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.