Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1301093

Summary: failed in UME with error 12 (Cannot allocate memory)
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: valgrindAssignee: Mark Wielaard <mjw>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dodji, jakub, mjw, mjw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: valgrind-3.11.0-8 valgrind-3.11.0-8.fc23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-28 18:23:17 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:    
Bug Blocks: 910269    

Description Richard W.M. Jones 2016-01-22 14:59:00 UTC
Description of problem:

All use of valgrind in Rawhide fails with:

  valgrind: mmap(0x600000, 8192) failed in UME with error 12 (Cannot allocate memory).

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

valgrind-3.11.0-5.fc24.x86_64
kernel-4.5.0-0.rc0.git7.1.fc24.x86_64 [see below]

How reproducible:

100%

Steps to Reproduce:
1. cat test.c
#include <stdlib.h>
int main ()
{
  exit (0);
}

2. gcc -o test test.c -g
3. valgrind test

Actual results:

valgrind: mmap(0x600000, 8192) failed in UME with error 12 (Cannot allocate memory).

Expected results:

Such a simple program shouldn't have any memory errors.

Additional info:

This was inconclusively reported upstream here:

http://sourceforge.net/p/valgrind/mailman/message/34755456/

It suggests it's a kernel bug or a change that was made in the Linux kernel.

Comment 1 Mark Wielaard 2016-01-22 15:05:16 UTC
Could you try with valgrind-3.11.0-8 which should include a fix for the change in kernel behaviour (). It was also submitted as an update for f23 (although that still uses a kernel with the original semantics for RLIMIT_DATA):
https://bodhi.fedoraproject.org/updates/FEDORA-2016-3795b5d3a9

Comment 2 Richard W.M. Jones 2016-01-22 15:17:02 UTC
Oh yes, that works (actually the -9 package).  Thanks!

Comment 3 Fedora Update System 2016-01-22 15:20:03 UTC
valgrind-3.11.0-8.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3795b5d3a9

Comment 4 Fedora Update System 2016-01-24 04:51:33 UTC
valgrind-3.11.0-8.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3795b5d3a9

Comment 5 Fedora Update System 2016-01-28 18:23:06 UTC
valgrind-3.11.0-8.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.