linux-kernel - Re: Regression: 2.6.34 boot fails on E5405 system, bisected: de08e2c26

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: <4C3E0641.4020706@zytor.com>
Date:	Wed, 14 Jul 2010 11:47:29 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ben Greear <greearb@...delatech.com>
CC:	"Pan, Jacob jun" <jacob.jun.pan@...el.com>,
	Robert Hancock <hancockrwd@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>
Subject: Re: Regression: 2.6.34 boot fails on E5405 system, bisected: 	de08e2c26

On 07/14/2010 11:22 AM, Ben Greear wrote:
> 
> Is there at least a maximum number of capabilities that can exist so that
> you can limit the loop by that?
> 

Well, 3072 bytes and a minimum size of 4 bytes, so 768.  However, a
capability ID of 0000 or FFFF means no capabilities (PCIe 2.01 sec
7.9.1-2), so we should terminate the search on finding one of those
capability ID.

[Also note: bits 21:20 are reserved and need to be masked, per PCIe 2.01
7.9.3.]

The spec seems to imply that capabilities should be sequential, but I
really don't know if that is actually the case in the field.

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/