Bug 1007400

Summary: /CoreOS/tar/Regression/bz518079-memory-leak-in-tar-xattr fails on ppc64
Product: Red Hat Enterprise Linux 6 Reporter: Alex Sersen <asersen>
Component: valgrindAssignee: Mark Wielaard <mjw>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: bblaskov, fche, jakub, mbenitez, mfranc, mprchlik, ohudlick, praiskup
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: valgrind-3.8.1-3.3.el6 Doc Type: Bug Fix
Doc Text:
Cause: Valgrind didn't support the [lf]setxattr system calls on ppc32 and ppc64 linux kernels. Consequence: Programs using those system calls when running under valgrind would get warnings and errors. Fix: valgrind now recognizes those system calls and handles them properly. Result: Programs running under valgrind on ppc that use [lf]setxattr system calls run without warnings or errors.
Story Points: ---
Clone Of: 977416 Environment:
Last Closed: 2014-10-14 06:36:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 977416    
Bug Blocks: 1056252    

Description Alex Sersen 2013-09-12 12:20:22 UTC
Same problem on RHEL6.5-20130830.2

+++ This bug was initially created as a clone of Bug #977416 +++

Description of problem:
valgrind fails with "WARNING: unhandled syscall: 209" error on ppc64 arch.
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2013/06/4360/436002/916777/13195208/TESTOUT.log


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


How reproducible:
run test [1] 

[1] http://pkgs.devel.redhat.com/cgit/tests/tar/tree/Regression/bz518079-memory-leak-in-tar-xattr
Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Alex Sersen on 2013-06-24 10:04:49 EDT ---

Affected version:
valgrind-3.5.0-5.el5

--- Additional comment from Mark Wielaard on 2013-07-04 16:35:04 EDT ---

209 is setxattr

--- Additional comment from Mark Wielaard on 2013-07-04 17:24:09 EDT ---

This is also a problem with upstream svn trunk.
I filed a bug and provided a patch:
https://bugs.kde.org/show_bug.cgi?id=321969

--- Additional comment from Mark Wielaard on 2013-07-05 05:52:39 EDT ---

This is now fixed upstream as svn commit r13449.

--- Additional comment from Mark Wielaard on 2013-07-08 17:45:38 EDT ---

Also in fedora valgrind-3.8.1-17 now.

Comment 4 Miloš Prchlík 2014-06-03 12:21:18 UTC
Verified for build valgrind-3.8.1-3.5.el6.

Comment 5 errata-xmlrpc 2014-10-14 06:36:52 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.

http://rhn.redhat.com/errata/RHBA-2014-1464.html