Bug 497540 - grp module does not support whole uid/gid range
grp module does not support whole uid/gid range
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: python (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Dave Malcolm
Petr Šplíchal
Depends On:
  Show dependency treegraph
Reported: 2009-04-24 10:46 EDT by Petr Šplíchal
Modified: 2016-05-31 21:37 EDT (History)
1 user (show)

See Also:
Fixed In Version: python-2.3.4-14.8.el4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-02-16 09:19:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
simple reproducer (107 bytes, text/plain)
2009-04-24 10:46 EDT, Petr Šplíchal
no flags Details

  None (edit)
Description Petr Šplíchal 2009-04-24 10:46:59 EDT
Created attachment 341183 [details]
simple reproducer

Description of problem:

In the current RHEL4 UIDs and GIDs are supported in the range
between 0-4294967295 on 64bit archs. However, python's module grp
does not support the full range.

This can cause problems as for example nfs-utils create upon
installation an nfsnobody user account/group with the UID/GID
of 4294967294.

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

How reproducible:

Steps to Reproduce:
1. groupadd -g 4294967294 nfsnobody
2. python test_grp.py

Actual results:
Traceback (most recent call last):
  File "test_grp.py", line 8, in ?
    e2 = grp.getgrgid(e.gr_gid)
OverflowError: signed integer is greater than maximum

Expected results:
No traceback.
Comment 2 Dave Malcolm 2010-08-20 13:03:06 EDT
Looks like this was fixed upstream in:
(change from int to unsigned int)

Looks trivial to backport.

This was part of this wider fix:

Another relevant 64-bit fix from that commit appears to be:

See also:
changing from using "I"/unsigned int extraction to PyNumber_Int
Comment 8 errata-xmlrpc 2011-02-16 09:19:34 EST
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 therefore 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.