linux-kernel - Re: FLR on AER

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] [day] [month] [year] [list]

Message-ID: <372f63b2-2739-51fe-8959-3c5a0fecc29e@codeaurora.org>
Date:   Thu, 22 Feb 2018 08:57:21 -0500
From:   Sinan Kaya <okaya@...eaurora.org>
To:     Jon Masters <jcm@...hat.com>, helgaas@...nel.org
Cc:     linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: FLR on AER

On 2/22/2018 8:21 AM, Jon Masters wrote:
> Hi Bjorn,
> 
> It looks like the AER driver won’t do a device FLR but instead will default to progressively bigger hammers. Am I missing something?
> 

AFAIK, AER driver does a secondary bus reset only if it observes a FATAL error. In order to
issue an FLR, driver needs to access the endpoint config space. Since there is a FATAL error,
this is not possible as PCI link is unreliable or probably gone.

> Jon.
> 


-- 
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.