From: Greg KH <greg@kroah.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ben Greear <greearb@candelatech.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/pci/mrst: add extra check in fixed bar detection
Date: Tue, 20 Jul 2010 12:08:26 -0700 [thread overview]
Message-ID: <20100720190826.GA16162@kroah.com> (raw)
In-Reply-To: <4C45DC30.5000308@zytor.com>
On Tue, Jul 20, 2010 at 10:26:08AM -0700, H. Peter Anvin wrote:
> On 07/20/2010 10:18 AM, Ben Greear wrote:
> > On 07/16/2010 11:58 AM, Jacob Pan wrote:
> >> Fixed bar capability structure is searched in PCI extended configuration
> >> space. We need to make sure there is a valid capability id to begin with
> >> otherwise, the search code may stuck in a infinite loop which results in
> >> boot hang.
> >> This patch adds additional check for cap ID 0, which is also invalid.
> >
> > I think this should be added to the stable tree for 2.6.34
> > as well...
> >
>
> Agreed. Greg, could you consider upstream
> f82c3d71d6fd2e6a3e3416f09099e29087e39abf for -stable 2.6.34?
Will do.
thanks,
greg k-h
prev parent reply other threads:[~2010-07-20 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 18:58 [PATCH] x86/pci/mrst: add extra check in fixed bar detection Jacob Pan
2010-07-16 19:12 ` Jesse Barnes
2010-07-17 0:49 ` [tip:x86/urgent] x86, pci, mrst: Add extra sanity check in walking the PCI extended cap chain tip-bot for Jacob Pan
2010-07-20 17:18 ` [PATCH] x86/pci/mrst: add extra check in fixed bar detection Ben Greear
2010-07-20 17:26 ` H. Peter Anvin
2010-07-20 19:08 ` Greg KH [this message]
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=20100720190826.GA16162@kroah.com \
--to=greg@kroah.com \
--cc=greearb@candelatech.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@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