Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
valgrind error for change-media and console for now, if there are more commands involved in this error, I 'll track them in this bug.
Version-Release number of selected component (if applicable):
libvirt-0.9.10-21.el6
How reproducible:
always
Steps to Reproduce:
1. # valgrind -v --leak-check=full virsh console rhel63
snip...
==15626== 1 errors in context 1 of 11:
==15626== Invalid read of size 4
==15626== at 0x30336CEA9F: virStreamFree (libvirt.c:15419)
==15626== by 0x40A671: vshRunConsole (console.c:394)
==15626== by 0x4167DE: cmdRunConsole (virsh.c:865)
==15626== by 0x416B9E: cmdConsole (virsh.c:899)
==15626== by 0x413CB4: vshCommandRun (virsh.c:18669)
==15626== by 0x423973: main (virsh.c:20261)
==15626== Address 0x4ea71b0 is 0 bytes inside a block of size 40 free'd
==15626== at 0x4A0595D: free (vg_replace_malloc.c:366)
==15626== by 0x303364F158: virFree (memory.c:310)
==15626== by 0x30336BA64B: virUnrefStream (datatypes.c:1109)
==15626== by 0x30336CEABF: virStreamFree (libvirt.c:15427)
==15626== by 0x40A850: virConsoleShutdown (console.c:103)
==15626== by 0x303364860E: virEventPollRunOnce (event_poll.c:490)
==15626== by 0x30336473B6: virEventRunDefaultImpl (event.c:247)
==15626== by 0x41C231: vshEventLoop (virsh.c:19440)
==15626== by 0x3033658D78: virThreadHelper (threads-pthread.c:161)
==15626== by 0x301A607850: start_thread (in /lib64/libpthread-2.12.so)
==15626== by 0x3019EE767C: clone (in /lib64/libc-2.12.so)
2. # valgrind -v virsh change-media 3 hdc /var/lib/libvirt/images/foo2.img
==16217== 1 errors in context 1 of 12:
==16217== Invalid read of size 1
==16217== at 0x4A07804: __GI_strlen (mc_replace_strmem.c:284)
==16217== by 0x3019F167F6: xdr_string (in /lib64/libc-2.12.so)
==16217== by 0x3033709E8D: xdr_remote_nonnull_string (remote_protocol.c:31)
==16217== by 0x303370E5CB: xdr_remote_domain_update_device_flags_args (remote_protocol.c:2028)
==16217== by 0x30337197D1: virNetMessageEncodePayload (virnetmessage.c:341)
==16217== by 0x30337135E1: virNetClientProgramCall (virnetclientprogram.c:327)
==16217== by 0x30336F1EFD: callWithFD (remote_driver.c:4586)
==16217== by 0x30336F1F7B: call (remote_driver.c:4607)
==16217== by 0x30336F42F2: remoteDomainUpdateDeviceFlags (remote_client_bodies.h:2865)
==16217== by 0x30336D46E5: virDomainUpdateDeviceFlags (libvirt.c:9457)
==16217== by 0x41AEE8: cmdChangeMedia (virsh.c:15249)
==16217== by 0x413CB4: vshCommandRun (virsh.c:18669)
==16217== Address 0x4ec5e25 is 0 bytes after a block of size 293 alloc'd
==16217== at 0x4A04A28: calloc (vg_replace_malloc.c:467)
==16217== by 0x303364F1DB: virAllocN (memory.c:129)
==16217== by 0x41A844: vshPrepareDiskXML (virsh.c:15043)
==16217== by 0x41AECC: cmdChangeMedia (virsh.c:15246)
==16217== by 0x413CB4: vshCommandRun (virsh.c:18669)
==16217== by 0x423973: main (virsh.c:20261)
Actual results:
defect errors.
Expected results:
no error.
Additional info:
(In reply to comment #0)
> Description of problem:
> valgrind error for change-media and console for now, if there are more
> commands involved in this error, I 'll track them in this bug.
It's actually easier for us if you file separate BZs for each. Thanks. -Davea
The problem in comment0 step1 is fixed , but i found someone doesn't appear before.I'm not sure whether is a new issue.
Something like below
Use of uninitialised value of size 8
==9161== at 0x39D9E04091: numa_node_size64 (in /usr/lib64/libnuma.so.1)
==9161== by 0x39D9E05A48: ??? (in /usr/lib64/libnuma.so.1)
==9161== by 0x39C2E0E534: _dl_init (in /lib64/ld-2.12.so)
==9161== by 0x39C2E00B39: ??? (in /lib64/ld-2.12.so)
==9161== by 0x2: ???
==9161== by 0x7FF00076E: ???
==9161== by 0x7FF000774: ???
==9161== by 0x7FF00077C: ???
See the attachenment for full details
(In reply to comment #7)
> (In reply to comment #6)
> > Created attachment 606752[details]
> > leak-full
>
> These leaks are irrelevant with libvirt, so you may close this bug IMHO.
thanks
Accroding comment 5 ,7 . verify this bug
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.
http://rhn.redhat.com/errata/RHSA-2013-0276.html