All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Benjamin Beier <benjamin@desaster-games.com>
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
	xen-devel@lists.xensource.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [BUG][4.5.1]xl cpupool-create segfault (with config file parameter)
Date: Wed, 26 Aug 2015 16:25:52 -0600	[thread overview]
Message-ID: <55DE3CF0.3060306@suse.com> (raw)
In-Reply-To: <55CC7BF6.8050002@desaster-games.com>

Benjamin Beier wrote:
> On 08/12/2015 01:28 PM, Ian Campbell wrote:
>> 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?
>
> I am not 100% sure about that, because I only had a test system
> running with it.
> As you guys didn't notice any problems I should mention that my
> servers are running Gentoo Linux.
> Maybe this is a Gentoo specific problem and not relevant at all for
> upstream xen.
> Or it is an upstream problem that only shows up on the custom-compiled
> gentoo systems.
>
> # cat testing
> foo
>
> # xl cpupool-create testing
> Segmentation fault
>
> # strace xl cpupool-create testing
> (...)
> open("testing", O_RDONLY)               = 7
> fstat(7, {st_mode=S_IFREG|0644, st_size=4, ...}) = 0
> fstat(7, {st_mode=S_IFREG|0644, st_size=4, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x776ec3228000
> read(7, "foo\n", 4096)                  = 4
> close(7)                                = 0
> munmap(0x776ec3228000, 4096)            = 0
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
> +++ killed by SIGSEGV (core dumped) +++
> Segmentation fault
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000418db5 in main_cpupoolcreate (argc=<optimized out>,
> argv=0x7fffffffda50) at xl_cmdimpl.c:7102
> 7102    xl_cmdimpl.c: No such file or directory.
> (gdb) bt
> #0  0x0000000000418db5 in main_cpupoolcreate (argc=<optimized out>,
> argv=0x7fffffffda50) at xl_cmdimpl.c:7102
> #1  0x0000000000407c79 in main (argc=2, argv=0x7fffffffda50) at xl.c:361

Sorry for jumping in late, but I encountered this issue yesterday with
4.5.1. Commit 705c9e12 fixes it and should probably be backported to the
4.5 branch.

Regards,
Jim

  parent reply	other threads:[~2015-08-26 22:25 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
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 [this message]
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=55DE3CF0.3060306@suse.com \
    --to=jfehlig@suse.com \
    --cc=benjamin@desaster-games.com \
    --cc=dario.faggioli@citrix.com \
    --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.