All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: xen-devel@lists.xensource.com
Subject: [patch] pv-on-hvm crash fix
Date: Wed, 23 May 2007 12:26:16 +0200	[thread overview]
Message-ID: <465416C8.1060209@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

   Hi,

The attached patch sets the error field in the statically allocated 
frontend and backend bus structs.  This is needed to make sure nobody 
ever tries to use them uninitialized.  Without that patch you can kill 
your machine by trying to load xen-vnif or xen-vblk on native hardware.

please apply,

   Gerd

[-- Attachment #2: xenpv-noxen.diff --]
[-- Type: text/x-patch, Size: 908 bytes --]

--- xenpv-3.1_15040/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_probe_backend.c.noxen	2007-05-22 16:16:53.000000000 +0200
+++ xenpv-3.1_15040/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_probe_backend.c	2007-05-22 16:17:31.000000000 +0200
@@ -115,6 +115,7 @@
 	.levels = 3, 		/* backend/type/<frontend>/<id> */
 	.get_bus_id = backend_bus_id,
 	.probe = xenbus_probe_backend,
+	.error = -ENODEV,
 	.bus = {
 		.name     = "xen-backend",
 		.match    = xenbus_match,
--- xenpv-3.1_15040/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_probe.c.noxen	2007-05-22 15:49:19.000000000 +0200
+++ xenpv-3.1_15040/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_probe.c	2007-05-22 16:16:30.000000000 +0200
@@ -172,6 +172,7 @@
 	.levels = 2, 		/* device/type/<id> */
 	.get_bus_id = frontend_bus_id,
 	.probe = xenbus_probe_frontend,
+	.error = -ENODEV,
 	.bus = {
 		.name     = "xen",
 		.match    = xenbus_match,

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2007-05-23 10:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=465416C8.1060209@redhat.com \
    --to=kraxel@redhat.com \
    --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.