All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Kris Shannon <kris@shannon.id.au>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Fix kernel NULL pointer dereference in xen-blkfront
Date: Wed, 4 Mar 2009 11:16:41 +0100	[thread overview]
Message-ID: <20090304101640.GY11787@kernel.dk> (raw)
In-Reply-To: <49ADA82A.6080508@goop.org>

On Tue, Mar 03 2009, Jeremy Fitzhardinge wrote:
> Kris Shannon wrote:
>> When booting Xen Dom0 on a pre-release 3.2.1 hypervisor the system Oopses on a
>> "Unable to handle kernel NULL pointer dereference" in xenwatch.
>>
>> From the backtrace it looks like backend_changed is calling bdget_disk
>> with a NULL pointer.  Checking for NULL and returning ENODEV instead
>> allows the kernel to boot.
>>   
>
> Thanks, applied.  (BTW, please cc: me and xen-devel for Xen-related  
> reports.)
>
> Jens: could you pull this; I think this is probably -rc material.  This  
> crash just started happening, so I guess its a side-effect of some core  
> kernel change.
>
> The following changes since commit c7241227f61ca6606a7fa3555391360d92bd8d9b:
>  Jens Axboe (1):
>        xen/blkfront: use blk_rq_map_sg to generate ring entries
>
> are available in the git repository at:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/frontend/blkfront
>
> Kris Shannon (1):
>      Fix kernel NULL pointer dereference in xen-blkfront
>
> drivers/block/xen-blkfront.c |    2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)

Sure, pulled.

-- 
Jens Axboe


      reply	other threads:[~2009-03-04 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  8:47 [PATCH] Fix kernel NULL pointer dereference in xen-blkfront Kris Shannon
2009-03-03 21:59 ` Jeremy Fitzhardinge
2009-03-03 21:59   ` Jeremy Fitzhardinge
2009-03-04 10:16   ` Jens Axboe [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=20090304101640.GY11787@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=jeremy@goop.org \
    --cc=kris@shannon.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.