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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
 <SA1PR12MB8120268B790E1FCF8CD185479517A@SA1PR12MB8120.namprd12.prod.outlook.com>
Date: Wed, 17 Sep 2025 12:01:03 +0000
From: "Verma, Devendra" <Devendra.Verma@....com>
To: Bjorn Helgaas <helgaas@...nel.org>, ALOK TIWARI <alok.a.tiwari@...cle.com>
CC: "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "mani@...nel.org"
	<mani@...nel.org>, "vkoul@...nel.org" <vkoul@...nel.org>,
	"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Simek,
 Michal" <michal.simek@....com>
Subject: RE: [External] : [PATCH v2 1/2] dmaengine: dw-edma: Add AMD MDB
 Endpoint Support

[AMD Official Use Only - AMD Internal Distribution Only]

> -----Original Message-----
> From: Bjorn Helgaas <helgaas@...nel.org>
> Sent: Tuesday, September 16, 2025 20:36
> To: ALOK TIWARI <alok.a.tiwari@...cle.com>
> Cc: Verma, Devendra <Devendra.Verma@....com>; bhelgaas@...gle.com;
> mani@...nel.org; vkoul@...nel.org; dmaengine@...r.kernel.org; linux-
> pci@...r.kernel.org; linux-kernel@...r.kernel.org; Simek, Michal
> <michal.simek@....com>
> Subject: Re: [External] : [PATCH v2 1/2] dmaengine: dw-edma: Add AMD MDB
> Endpoint Support
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> On Tue, Sep 16, 2025 at 04:25:49PM +0530, ALOK TIWARI wrote:
> >
> >
> > On 9/16/2025 4:13 PM, Devendra K Verma wrote:
> > > +   /*
> > > +    * Synopsys and AMD (Xilinx) use the same VSEC ID for the purpose
> > > +    * of map, channel counts, etc.
> > > +    */
> > > +   if (vendor != PCI_VENDOR_ID_SYNOPSYS ||
> > > +       vendor != PCI_VENDOR_ID_XILINX)
> > > +           return;
> >
> > if, vendor == PCI_VENDOR_ID_XILINX condition will true
> >
> > should not be if (vendor != PCI_VENDOR_ID_SYNOPSYS && vendor !=
> > PCI_VENDOR_ID_XILINX) ?
>
> Good catch, I mistakenly said this part was correct, but you're right; it's obviously
> broken.
>
> The alternate structure I suggested would avoid this problem.
>
> > > +
> > > +   cap = DW_PCIE_VSEC_DMA_ID;
> > > +   if (vendor == PCI_VENDOR_ID_XILINX)
> > > +           cap = DW_PCIE_XILINX_MDB_VSEC_ID;
> > > +
> > > +   vsec = pci_find_vsec_capability(pdev, vendor, cap);
> > >     if (!vsec)
> >
> >
> > Thanks,
> > Alok

Thanks for noticing it, this was quickly corrected and updated in v3 of the same patch.

Regards,
Devendra

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ