From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: levinsasha928@gmail.com, kvm@vger.kernel.org
Subject: Re: [PATCH -V2] tools/kvm/9p: Add encode/decode routines for protocol data
Date: Mon, 27 Jun 2011 15:05:13 +0530 [thread overview]
Message-ID: <87mxh3pqge.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106271035320.12018@tiger>
On Mon, 27 Jun 2011 10:35:49 +0300 (EEST), Pekka Enberg <penberg@kernel.org> wrote:
> This breaks 'make check':
>
> ./kvm run -d tests/boot/boot_test.iso -p "init=init"
> Error: unknown switch `d'
>
> usage: kvm run [<options>] [<kernel image>]
>
> Basic options:
> -0, make: *** [check] Segmentation fault
>
>
I am able to reproduce this on debian x86_64. A simple test as below
kvm run -sda will result in segfault. I am find the option array
corrupt. Not yet sure why the patch would make a difference. Here
is the gdb dump of the structure
====Not working dump====
(gdb) p *(opts)
$5 = {type = OPTION_GROUP, short_name = 0, long_name = 0x0, value = 0x0, argh = 0x0, help = 0x40f2b0 "Basic options:", flags = 0,
callback = 0, defval = 38654705664}
(gdb) p *(opts+1)
$6 = {type = 99, short_name = 4256447, long_name = 0x61551800000000 <Address 0x61551800000000 out of bounds>, value = 0x0,
argh = 0x40f2c400000000 <Address 0x40f2c400000000 out of bounds>, help = 0x0, flags = 0, callback = 0, defval = 468151435276}
(gdb)
==== Working dump ====
(gdb) p *(opts)
$4 = {type = OPTION_GROUP, short_name = 0, long_name = 0x0, value = 0x0, argh = 0x0, help = 0x40e9b0 "Basic options:", flags = 0,
callback = 0, defval = 0}
(gdb) p *(opts+1)
$5 = {type = OPTION_INTEGER, short_name = 99, long_name = 0x40e9bf "cpus", value = 0x6151c8, argh = 0x0, help = 0x40e9c4 "Number of CPUs",
flags = 0, callback = 0, defval = 0}
(gdb)
next prev parent reply other threads:[~2011-06-27 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 6:05 [PATCH -V2] tools/kvm/9p: Add encode/decode routines for protocol data Aneesh Kumar K.V
2011-06-27 7:35 ` Pekka Enberg
2011-06-27 9:35 ` Aneesh Kumar K.V [this message]
2011-06-27 10:28 ` Aneesh Kumar K.V
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=87mxh3pqge.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=penberg@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