mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Don Dutile <ddutile@redhat.com>
Subject: Re: [PATCH resend] pci: ARI is a PCIe v2 feature
Date: Thu, 14 Jul 2011 01:16:19 -0700	[thread overview]
Message-ID: <20110714081619.GB15844@sequoia.sous-sol.org> (raw)
In-Reply-To: <20110714153533.7f310cdf@jbarnes-e6510>

* Jesse Barnes (jbarnes@virtuousgeek.org) wrote:
> On Wed, 13 Jul 2011 10:14:33 -0700
> Chris Wright <chrisw@sous-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.

Cool, just wanted to make sure it wasn't lost.  I think it's fine to
merge in next window and let it filter back to -stable.  While I've seen
it cause panics, it's not a regression and the conditions required are
very specific (possibly including buggy BIOS).

thanks,
-chris

  reply	other threads:[~2011-07-14  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 17:14 Chris Wright
2011-07-14  7:35 ` Jesse Barnes
2011-07-14  8:16   ` Chris Wright [this message]
2011-07-22 15:44 ` Jesse Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110714081619.GB15844@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=ddutile@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®