From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>, xen-devel@lists.xensource.com
Subject: Re: Re: Null-pointer access in netback_uevent
Date: Thu, 27 May 2010 15:39:16 -0700 [thread overview]
Message-ID: <4BFEF494.6090508@goop.org> (raw)
In-Reply-To: <20100527222708.GB25018@wavehammer.waldi.eu.org>
On 05/27/2010 03:27 PM, Bastian Blank wrote:
> On Thu, May 27, 2010 at 02:03:15PM -0700, Jeremy Fitzhardinge wrote:
>
>> On 05/27/2010 09:55 AM, Bastian Blank wrote:
>>
>>> My slightly patched kernel based on
>>> f6fe6583b77a49b569eef1b66c3d761eec2e561b failed with null-pointer access in
>>> netback_uevent.
>>>
>> What were you doing at the time?
>>
> Domain creation.
>
Using the xm toolset? Has it always crashed, or was there some change
which made it start happening? Or is it an erratic failure?
J
next prev parent reply other threads:[~2010-05-27 22:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 16:55 Null-pointer access in netback_uevent Bastian Blank
2010-05-27 21:03 ` Jeremy Fitzhardinge
2010-05-27 22:27 ` Bastian Blank
2010-05-27 22:39 ` Jeremy Fitzhardinge [this message]
2010-05-27 23:02 ` Bastian Blank
2010-05-28 0:04 ` James Harper
2010-05-28 0:33 ` James Harper
2010-05-28 0:47 ` James Harper
2010-05-28 9:03 ` Bastian Blank
2010-05-28 17:28 ` Jeremy Fitzhardinge
2010-05-28 22:42 ` James Harper
2010-05-28 23:30 ` Jeremy Fitzhardinge
2010-05-28 23:59 ` James Harper
2010-05-29 6:44 ` Bastian Blank
2010-05-29 18:44 ` [PATCH] xen/netback: Fix null-pointer " Bastian Blank
2010-05-31 7:37 ` Jan Beulich
2010-05-31 8:07 ` Jan Beulich
2010-07-28 16:20 ` Bastian Blank
2010-07-29 11:47 ` Ian Campbell
2010-07-29 12:42 ` Bastian Blank
2010-07-29 13:44 ` Ian Campbell
2010-07-29 13:48 ` Ian Campbell
2010-07-29 15:30 ` Bastian Blank
2010-07-29 15:40 ` Jeremy Fitzhardinge
2010-07-29 17:08 ` Bastian Blank
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=4BFEF494.6090508@goop.org \
--to=jeremy@goop.org \
--cc=waldi@debian.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.