linux-kernel - Re: [PATCH 1/1][resend] check for pci bar restore completion and retry

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: <20120127114416.2621963a@jbarnes-desktop>
Date:	Fri, 27 Jan 2012 11:44:16 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	"Kay, Allen M" <allen.m.kay@...el.com>
Cc:	"linux-pci-owner@...r.kernel.org" <linux-pci-owner@...r.kernel.org>,
	"Barnes, Jesse" <jesse.barnes@...el.com>,
	"Wilcox, Matthew R" <matthew.r.wilcox@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"jean.guyader@...citrix.com" <jean.guyader@...citrix.com>,
	"eric.chanudet@...rix.com" <eric.chanudet@...rix.com>
Subject: Re: [PATCH 1/1][resend]  check for pci bar restore completion and
 retry

On Thu, 26 Jan 2012 10:25:53 -0800
"Kay, Allen M" <allen.m.kay@...el.com> wrote:

> On some OEM systems, pci_restore_state() is called while FLR has not yet
> completed.  As a result, PCI BAR register restore is not successful.  This fix
> reads back the restored value and compares it with saved value and re-tries 10
> times before giving up.

Applied, but I don't think I got an answer as to why we don't do this
delay/check when we perform the FLR in the first place?

-- 
Jesse Barnes, Intel Open Source Technology Center

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)