Bug 130965 - personality syscall parameters not decoded
Summary: personality syscall parameters not decoded
Alias: None
Product: Fedora
Classification: Fedora
Component: strace
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Roland McGrath
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-26 05:57 UTC by Ulrich Drepper
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2004-09-01 02:03:04 UTC

Attachments (Terms of Use)
Patch to implement PER_ option decoding (1.03 KB, patch)
2004-08-26 06:00 UTC, Ulrich Drepper
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:131 normal SHIPPED_LIVE strace bug fix update 2005-05-19 04:00:00 UTC

Description Ulrich Drepper 2004-08-26 05:57:25 UTC
Description of problem:
The parameters of the personality syscall are not decoded.  This has
two reasons:
a) the PER_ values are no macros, so all the #ifdef PER_xxx tests fail
b) a number of values are missing

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

How reproducible:

Steps to Reproduce:
1.strace setarch -3 i386 /bin/echo
Actual results:
personality(0x8000008 /* PER_??? */)    = 0

Expected results:
personality(PER_LINUX32_3GB)            = 0

Additional info:
I'll attach a patch.

Comment 1 Ulrich Drepper 2004-08-26 06:00:54 UTC
Created attachment 103111 [details]
Patch to implement PER_ option decoding

The patch assumes that recent kernel headers are available since we cannot test
using #ifdef whether the PER_ values are defined.  The only alternative is to
define the value in system.c and not rely on kernel headers.  Your choice.

Comment 2 Roland McGrath 2004-08-31 06:46:39 UTC
I put a fix in upstream.

Comment 3 Roland McGrath 2004-09-01 02:03:04 UTC
4.5.7-2 is in rawhide.  I'll make an FC2 update release in a few days.

Comment 4 Tim Powers 2005-05-19 21:09:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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