Bug 1538570 - Segmentation fault when run some virt-admin help srv* cmd.
Summary: Segmentation fault when run some virt-admin help srv* cmd.
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Erik Skultety
QA Contact: Lili Zhu
Depends On:
TreeView+ depends on / blocked
Reported: 2018-01-25 10:29 UTC by zhe peng
Modified: 2018-10-30 09:54 UTC (History)
4 users (show)

Fixed In Version: libvirt-4.3.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-10-30 09:52:39 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3113 None None None 2018-10-30 09:54:42 UTC

Description zhe peng 2018-01-25 10:29:15 UTC
Description of problem:
Segmentation fault when run some virt-admin help srv* cmd.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.install libvirt-admin pkg
2.# virt-admin help srv-clients-set
    srv-clients-set - (null)

Segmentation fault (core dumped)

same with cmd srv-threadpool-set,srv-clients-info,srv-threadpool-info,srv-clients-list

actually srv-* cmd removed in help contents.
Monitoring commands (help keyword 'monitor'):
    server-list                    list available servers on a daemon
    server-threadpool-info         get server workerpool parameters
    client-list                    list clients connected to <server>
    client-info                    retrieve client's identity info from server
    server-clients-info            get server's client-related configuration limits

 Management commands (help keyword 'management'):
    server-threadpool-set          set server workerpool parameters
    client-disconnect              force disconnect a client from the given server
    server-clients-set             set server's client-related configuration limits
    daemon-log-filters             fetch or set the currently defined set of logging filters on daemon
    daemon-log-outputs             fetch or set the currently defined set of logging outputs on daemon

Actual results:

Expected results:
if virt-admin use server* instead of srv*, we hope no Segmentation fault and
error msg like this:
error: command or command group 'srv*' doesn't exist

Additional info:

Comment 1 Erik Skultety 2018-01-25 16:09:38 UTC
Fixed upstream by:

commit 23594ccda9d0813c1b019db7348d9e93f20bb884
Refs: v4.0.0-26-g23594ccda
Author:     Erik Skultety <eskultet@redhat.com>
AuthorDate: Thu Jan 25 16:13:37 2018 +0100
Commit:     Erik Skultety <eskultet@redhat.com>
CommitDate: Thu Jan 25 16:20:27 2018 +0100

    vsh: Cmd aliases lookups should return results for the aliased command

    Unfortunately, we have a number of aliases in virsh and even though
    these are not visible any more, we have to support them. The problem is
    that when trying to print help for the alias, we get SIGSEGV because
    there isn't any @def structure anymore and we need to query the command
    being aliased instead.

    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1538570

    Signed-off-by: Erik Skultety <eskultet@redhat.com>

Comment 3 Lili Zhu 2018-06-15 07:10:07 UTC
Verify this bug with:

1. print help for virsh cmd alias
# virsh help nodedev-dettach
    nodedev-detach - detach node device from its device driver

    nodedev-detach <device> [--driver <string>]

2. print help for virt-admin cmd alias
# virt-admin help srv-list 
    server-list - list available servers on a daemon


I also try to print help other cmd aliases of virt-admin, including srv-threadpool-info, srv-clients-info, srv-threadpool-set, srv-clients-set, all of them work well.

As the result matches with the expected result, mark the bug as verified.

Comment 5 errata-xmlrpc 2018-10-30 09:52:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.