From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xenbus: fix possible crash in xenbus_uevent_backend
Date: Mon, 18 Jul 2011 17:02:58 +0200 [thread overview]
Message-ID: <20110718150258.GA13123@aepfle.de> (raw)
In-Reply-To: <1310994684.20648.47.camel@zakaz.uk.xensource.com>
On Mon, Jul 18, Ian Campbell wrote:
> On Mon, 2011-07-18 at 13:40 +0100, Olaf Hering wrote:
> > Fix possible NULL pointer crash in xenbus_uevent_backend().
> > The variable to check for should probably be bus.
> >
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> >
> > Index: linux-3.0-rc7-xen-kexec/drivers/xen/xenbus/xenbus_probe_backend.c
> > ===================================================================
> > --- linux-3.0-rc7-xen-kexec.orig/drivers/xen/xenbus/xenbus_probe_backend.c
> > +++ linux-3.0-rc7-xen-kexec/drivers/xen/xenbus/xenbus_probe_backend.c
> > @@ -104,7 +104,7 @@ static int xenbus_uevent_backend(struct
> >
> > xdev = to_xenbus_device(dev);
> > bus = container_of(xdev->dev.bus, struct xen_bus_type, bus);
> > - if (xdev == NULL)
> > + if (bus == NULL)
> > return -ENODEV;
>
> Is this fixing an actual crash which you observed of just something you
> noticed looking at the code?
I was browsing the code.
Thanks to you and Jan for reviewing my attempt to fix something thats
not broken. I will prepare a better patch.
Olaf
next prev parent reply other threads:[~2011-07-18 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 12:40 [PATCH] xenbus: fix possible crash in xenbus_uevent_backend Olaf Hering
2011-07-18 13:11 ` Ian Campbell
2011-07-18 13:21 ` Jan Beulich
2011-07-18 13:26 ` Ian Campbell
2011-07-18 15:02 ` Olaf Hering [this message]
2011-07-18 13:18 ` Jan Beulich
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=20110718150258.GA13123@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.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.