public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Greg KH <greg@kroah.com>
Cc: Alex Chiang <achiang@hp.com>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
	stable@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [stable] [BUG][PATCH] cpqphp: fix kernel NULL pointer dereference
Date: Thu, 23 Oct 2008 14:36:43 -0700	[thread overview]
Message-ID: <200810231436.44308.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081023203732.GA17600@kroah.com>

On Thursday, October 23, 2008 1:37 pm Greg KH wrote:
> On Thu, Oct 16, 2008 at 06:33:34PM -0600, Alex Chiang wrote:
> > * Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>:
> > > The root cause of this problem seems that cpqphp driver calls
> > > pci_hp_register() wrongly. In current implementation, cpqphp driver
> > > passes 'ctrl->pci_dev->subordinate' as a second parameter for
> > > pci_hp_register(). But because hotplug slots and it's hotplug
> > > controller (exists as a pci funcion) are on the same bus, it should be
> > > 'ctrl->pci_dev->bus' instead.
> > >
> > > Cc: <stable@kernel.org>
> >
> > Acked-by: Alex Chiang <achiang@hp.com>
>
> This patch doesn't seem to have made it upstream.
>
> Jesse, is it queued up in any of your trees?

No I missed it initially.  I've got it queued up now though.

Jesse

  reply	other threads:[~2008-10-23 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  0:23 [BUG][PATCH] cpqphp: fix kernel NULL pointer dereference Kenji Kaneshige
2008-10-17  0:33 ` Alex Chiang
2008-10-23 20:37   ` [stable] " Greg KH
2008-10-23 21:36     ` Jesse Barnes [this message]
2008-10-23 21:46 ` 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=200810231436.44308.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=achiang@hp.com \
    --cc=greg@kroah.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    --cc=yinghai@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