This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/5227] O_ATOMICLOOKUP vs O_CLOEXEC problems with RHEL4 and RHEL5 kernels
- From: "Axel dot Thimm at ATrpms dot net" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 28 Dec 2007 01:53:52 -0000
- Subject: [Bug libc/5227] O_ATOMICLOOKUP vs O_CLOEXEC problems with RHEL4 and RHEL5 kernels
- References: <20071028012138.5227.john@thesalmons.org>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From Axel dot Thimm at ATrpms dot net 2007-12-28 01:53 -------
Note that this is still the case with RHEL5 as well.
I agree that vendors undefining or redefining constants is a very bad thing, but
at this point this kind of setup is really widely deployed. Given that Ulrich is
even working for that vendor, could there be some solution/workaround for
RHEL4/RHEL5 users? Maybe something like the *ASSUME_KERNEL environment setting?
A consequence of this bug is that all build systems based on RHEL5 carrying
Fedora chroots or for that matter any glibc 2.7 system are randomly breaking
with unknown error 530 (actually I don't understand why this is random and not
always, but that's probably another story). Other systems seem to suffer in a
similar way and browsing through google's "unknown error 530" hits one sees that
no user is even close to suspecting a kernel/glibc ABI incompatibility.
Is there any way to keep those Fedora 8/9 chroots running on a RHEL5 kernel? I'm
reopening not to pin that as a glibc bug, but as a request for a workaround or
advice for action to take. People desperately googling for "unknown error 530"
(like I did) will eventually find this report and would like to see what they
can do to fix it. Help! :)
I also filed this bug against the vendor as he should also take action to fix
these problems with the next kernel release (which according to the vendor's
schedule would happen the earliest in three months after a submission):
https://bugzilla.redhat.com/show_bug.cgi?id=426890
Thanks for any advice in advance!
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |Axel dot Thimm at ATrpms dot
| |net
Status|RESOLVED |REOPENED
Resolution|INVALID |
Summary|opendir and O_CLOEXEC |O_ATOMICLOOKUP vs O_CLOEXEC
|problems with Linux-2.6.9- |problems with RHEL4 and
|5.ELsmp kernel |RHEL5 kernels
http://sourceware.org/bugzilla/show_bug.cgi?id=5227
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.