Bug 106684 - getgrnam fails with invalid group and long group line
Summary: getgrnam fails with invalid group and long group line
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: glibc
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-09 16:04 UTC by Seth Lepzelter
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version: 2.3.2-90
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-17 18:14:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
simple test code (126 bytes, text/plain)
2003-10-09 16:07 UTC, Seth Lepzelter 		no flags Details
group file that causes the problem (1.19 KB, text/plain)
2003-10-09 16:08 UTC, Seth Lepzelter 		no flags Details
View All

Description Seth Lepzelter 2003-10-09 16:04:08 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
Gecko/20021120 Netscape/7.01

Description of problem:
getgrnam goes into an infinite loop (reading /etc/group over and over) when
(symptom was tar, but a simple test program fails as well).

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

How reproducible:
Always

Steps to Reproduce:
1. look up a non-existant group
2. use the attached group file

Actual Results:  calls to getgrnam never return, read /etc/group indefinitely

Expected Results:  should return NULL

Additional info:
Comment 1 Seth Lepzelter 2003-10-09 16:07:55 UTC 
Created attachment 95075 [details]
simple test code
Comment 2 Seth Lepzelter 2003-10-09 16:08:53 UTC 
Created attachment 95076 [details]
group file that causes the problem
Comment 3 Seth Lepzelter 2003-10-17 17:38:17 UTC 
This appears to be fixed in the 2.3.2-90 release of glibc.
Comment 4 Jakub Jelinek 2003-10-17 18:14:13 UTC 
I was wondering why I cannot reproduce it...
Note You need to log in before you can comment on or make changes to this bug.