xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Benjamin Beier <benjamin@desaster-games.com>,
	xen-devel@lists.xensource.com
Cc: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [BUG][4.5.1]xl cpupool-create segfault (with config file parameter)
Date: Wed, 12 Aug 2015 12:28:51 +0100	[thread overview]
Message-ID: <1439378931.8356.20.camel@citrix.com> (raw)
In-Reply-To: <55CB27F2.60903@desaster-games.com>

On Wed, 2015-08-12 at 13:03 +0200, Benjamin Beier wrote:
> Since xen version 4.5.1 there is a bug with the xl cpupool-create 
> command.
> It always throws a segmentation fault when used with a config file as 
> parameter.
> The content of the config file does not really matter (valid or invalid).
> It also fails with the example config file in /etc/xen/cpupool or with 
> the dryrun flag.
> You never get any output apart from "segmentation fault".
> If you create exactly the same cpupool without using a config file it 
> works absolutely fine.
> Tested on multiple systems and it seems to be reproducible for everyone.
> STrace shows that the command fails right after reading the content of 
> the config file.

Please can you capture a backtrace by running it under gdb. Valgrind might
also have something interesting to say.

FWIW this doesn't happen on the current development branch:
    # cat foo
    Testing
    # xl cpupool-create foo
    foo:1: config parsing error near `Testing': lexical error
    Failed to parse config file: Invalid argument

But I don't see any obviously related looking fixes in the commit log.

Was 4.5.0 ok?

Ian.

  reply	other threads:[~2015-08-12 11:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 11:03 [BUG][4.5.1]xl cpupool-create segfault (with config file parameter) Benjamin Beier
2015-08-12 11:28 ` Ian Campbell [this message]
2015-08-13  9:01   ` Dario Faggioli
2015-08-13 11:13   ` Benjamin Beier
2015-08-13 11:29     ` Ian Campbell
2015-08-13 12:12       ` Benjamin Beier
2015-08-26 22:25     ` Jim Fehlig
2015-09-01 11:18       ` Ian Campbell
2015-09-01 11:29         ` Ian Jackson

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=1439378931.8356.20.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=benjamin@desaster-games.com \
    --cc=dario.faggioli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).