linux-kernel - Re: [PATCH] pci/doe: add a 1 second retry window to pci

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: <20240916101557.00007b3a@Huawei.com>
Date: Mon, 16 Sep 2024 10:15:57 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Dan Williams <dan.j.williams@...el.com>
CC: Gregory Price <gourry@...rry.net>, <linux-pci@...r.kernel.org>,
	<linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<bhelgaas@...gle.com>, <dave@...olabs.net>, <dave.jiang@...el.com>,
	<vishal.l.verma@...el.com>, <lukas@...ner.de>
Subject: Re: [PATCH] pci/doe: add a 1 second retry window to pci_doe

On Fri, 13 Sep 2024 22:32:28 -0700
Dan Williams <dan.j.williams@...el.com> wrote:

> [ add linux-pci and Lukas ]
> 
> Gregory Price wrote:
> > Depending on the device, sometimes firmware clears the busy flag
> > later than expected.  This can cause the device to appear busy when
> > calling multiple commands in quick sucession. Add a 1 second retry
> > window to all doe commands that end with -EBUSY.  
> 
> I would have expected this to be handled as part of finishing off
> pci_doe_recv_resp() not retrying on a new submission.
> 
> It also occurs to me that instead of warning "another entity is sending conflicting
> requests" message, the doe core should just ensure that it is the only
> agent using the mailbox. Something like hold the PCI config lock over
> DOE transactions. Then it will remove ambiguity of "conflicting agent"
> vs "device is slow to clear BUSY".
> 

I believe we put that dance in to not fail too horribly
if a firmware was messing with the DOE behind our backs rather than
another OS level actor was messing with it.

We wouldn't expect firmware to be using a DOE that Linux wants, but
the problem is the discovery protocol which the firmware might run
to find the DOE it does want to use.

My memory might be wrong though as this was a while back.

Jonathan