Bug 17783 - fcntl may be broken in glibc 2.1.93-3.
fcntl may be broken in glibc 2.1.93-3.
Product: Red Hat Linux
Classification: Retired
Component: elm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Depends On:
  Show dependency treegraph
Reported: 2000-09-22 00:17 EDT by Red Hat Bugzilla
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-22 14:01:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Red Hat Bugzilla 2000-09-22 00:17:47 EDT
Please see


It is elm-2.5.3-9 and glibc-2.1.93-3 in RedHat 7.0
Comment 1 Red Hat Bugzilla 2000-09-22 01:45:14 EDT
To verify, please enable nscd so that fcntl on the mail folder is the first
fcntl call.
Comment 2 Red Hat Bugzilla 2000-09-22 03:19:04 EDT
I submitted a patch:

Comment 3 Red Hat Bugzilla 2000-09-22 07:46:06 EDT
Andreas is right on this, it is really an elm bug and should be fixed
Comment 4 Red Hat Bugzilla 2000-09-22 10:46:25 EDT
I agree elm is broken on this. But glibc drops the balls when it fails to
save/restore errno
when trying new system calls. Please keep in mind that many applications may do
Some may be broken like elm, but some may not.  Even if they are broken, do you
some Red Hat customers telll you their applications, which work under 6.2,  now
working in 7.0? Both elm and glibc should be fixed.
Comment 5 Red Hat Bugzilla 2000-09-22 14:01:02 EDT
No, glibc is not broken.  No program must check errno after a function call
didn't fail unless this explicitly documented.  This is just hiding bugs and
Comment 6 Red Hat Bugzilla 2000-10-23 11:44:26 EDT
Fixed (by not looking at errno when fcntl returns 0) in elm-2.5.3-10.

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