Glibc bug in RHEL4.6, OEL4.6, RHEL5.1, OEL5.1

There is a bug in glibc with calloc() not returning zeroed memory when the process address space is locked, for instance by a call to mlockall(). Versions of glibc affected are:

* RHEL-4.6 and OEL-4.6: glibc-2.3.4-2.39, all architectures.
* RHEL-5.1 and OEL-5.1: glibc-2.5-18, all achitectures.
* SLES10 SP2: glibc-2.4-31.54 , all architectures

This produces various symptoms including segmentation faults. Oracle CRS, the cssd process, as of 10.2.0.4 and higher, use the mlockall() call, and can fail. CRS versions prior to 10.2.0.4 do not use this call, and aren't effected.

Details on the problem are posted here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473812
https://bugzilla.redhat.com/show_bug.cgi?id=405781
https://bugzilla.novell.com/show_bug.cgi?id=416838

This bug has been fixed in RHEL5.2 glibc and OEL5.2 (glibc-2.5-54). It is also fixed in RHEL4.7 and OEL4.7 (glibc-2.3.4-2.41). For SLES10 SP2, it is fixed in glibc-2.4-31.63, or just use SP3. The bug was not present in earlier versions of glibc and it is not present in RHEL3.
Please see Metalink Note 732847.1

Comments:

can you post the metalink doc please? it is not published

Posted by thomas flatley on August 21, 2008 at 01:26 AM EDT #

The info in the Metalink note is the same as in my blog entry. You do need to log in to read Metalink notes. Only additional information is the Oracle bug number, which is: 6790001

Posted by Elena Zannoni on August 22, 2008 at 02:23 AM EDT #

Post a Comment:
Comments are closed for this entry.
About

Linux Tools News and Tidbits

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today