linux-kernel - Re: PCI VPD checksum ambiguity

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: <CALs4sv3awP3oA3-mvjSUmHCk=KZjF5F75SnnaE79ZUGqDC=orw@mail.gmail.com>
Date: Wed, 2 Apr 2025 16:03:42 +0530
From: Pavan Chebbi <pavan.chebbi@...adcom.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Heiner Kallweit <hkallweit1@...il.com>, Michael Chan <mchan@...adcom.com>, 
	Potnuri Bharat Teja <bharat@...lsio.com>, netdev@...r.kernel.org, linux-pci@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Leon Romanovsky <leon@...nel.org>
Subject: Re: PCI VPD checksum ambiguity

> > >
> > > Any idea how devices in the field populate their VPD?
> > >

I took a quick look at our manufacturing tool, and it does look like
the computation simply starts at address 0.

> > > Can you share any VPD dumps from devices that include an RV keyword
> > > item?

A couple of devices I could find: hope it helps..
000100: 822f0042 726f6164 636f6d20 4e657458 7472656d 65204769 67616269 74204574
000120: 6865726e 65742043 6f6e7472 6f6c6c65 7200904b 00504e08 42434d39 35373230
000140: 45430931 30363637 392d3135 534e0a30 31323334 35363738 394d4e04 31346534
000160: 52561d1d 00000000 00000000 00000000 000000

000100: 822f0042 726f6164 636f6d20 4e657458 7472656d 65204769 67616269 74204574
000120: 6865726e 65742043 6f6e7472 6f6c6c65 7200904b 00504e08 42434d39 35373139
000140: 45430931 30363637 392d3135 534e0a30 31323334 35363738 394d4e04 31346534
000160: 52561d15 00000000 00000000 00000000 00000000 00000000 00000000 00000000

> >
> > I have only very dated devices which likely date back to before
> > the existence of PCIe r6.0. So their VPD dump may not really help.
> >
> > IIRC there's an ongoing discussion regarding making VPD content
> > user-readable on mlx5 devices. Maybe check with the Mellanox/Nvidia
> > guys how they interpret the spec and implemented VPD checksumming.
>
> Good idea, cc'd.

Download attachment "smime.p7s" of type "application/pkcs7-signature" (4196 bytes)