linux-kernel - Re: [PATCH resend] pci: ARI is a PCIe v2 feature

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: <20110714153533.7f310cdf@jbarnes-e6510>
Date:	Thu, 14 Jul 2011 15:35:33 +0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Don Dutile <ddutile@...hat.com>
Subject: Re: [PATCH resend] pci: ARI is a PCIe v2 feature

On Wed, 13 Jul 2011 10:14:33 -0700
Chris Wright <chrisw@...s-sol.org> wrote:

> The function pci_enable_ari() may mistakenly set the downstream port
> of a v1 PCIe switch in ARI Forwarding mode.  This is a PCIe v2
> feature, and with an SR-IOV device on that switch port believing the
> switch above is ARI capable it may attempt to use functions 8-255,
> translating into invalid (non-zero) device numbers for that bus.
> This has been seen to cause Completion Timeouts and general
> misbehaviour including hangs and panics.


Thanks Chris, your earlier one is still sitting in my queue, but I
wasn't going to send it for 3.0 as it didn't seem that critical.  Do
you think it is?  If so you can send it directly to Linus with my ack
as I don't have anything else queued, or just wait until the merge
window when it will be put into the stable tree as well.

Thanks,
Jesse
--
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/