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 450976 - capget syscall can have NULL second parameter
Summary: capget syscall can have NULL second parameter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F10Target
TreeView+ depends on / blocked
 
Reported: 2008-06-12 01:14 UTC by Ulrich Drepper
Modified: 2010-04-27 02:20 UTC (History)
1 user (show)

Fixed In Version: valgrind-3.5.0-16.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-12 13:40:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Fix capget handling. (1.70 KB, patch)
2008-06-12 01:14 UTC, Ulrich Drepper 		no flags Details | Diff
View All

Description Ulrich Drepper 2008-06-12 01:14:06 UTC 
Description of problem:
The capget syscall implementation has a hack which can be used to get the
version number of the capability in the kernel.  For this the second parameter
is set to NULL.  This will in any case return EFAULT but as a side effect might
modify the second parameter.

Also, for x86-64 the syscall is not handled at all.


Version-Release number of selected component (if applicable):
valgrind-3.3.0-3.3.x86_64

How reproducible:
always

Steps to Reproduce:
1.try to run nscd under valgrind
2.
3.
  
Actual results:
complains about NULL parameter to capget

Expected results:
no message

Additional info:
I'll attach a patch.
Comment 1 Ulrich Drepper 2008-06-12 01:14:06 UTC 
Created attachment 309018 [details]
Fix capget handling.
Comment 2 John Poelstra 2008-07-04 04:11:58 UTC 
triaged
Comment 3 Bug Zapper 2008-11-26 02:24:56 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Bug Zapper 2009-11-18 12:34:45 UTC 
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Bug Zapper 2009-12-18 06:12:46 UTC 
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 6 Ulrich Drepper 2009-12-18 06:42:10 UTC 
The problem is still present in F12.
Comment 7 Jakub Jelinek 2010-04-12 13:40:36 UTC 
Sorry, should be fixed in valgrind-3.5.0-16.fc{12,13,14}.
Comment 8 Fedora Update System 2010-04-12 13:45:09 UTC 
valgrind-3.5.0-16.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/valgrind-3.5.0-16.fc13
Comment 9 Fedora Update System 2010-04-27 02:20:08 UTC 
valgrind-3.5.0-16.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.