|
Problem IC68444
|
Status: Geschlossen |
MEMORY ALLOCATION DOES NOT SANITY CHECK SIZE REQUESTED ON 64 BIT PLATFORM. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
On 64 bit platform, when memory manager is asked to allocate
huge size of memory, it does not check if the asked 'size' is
too big. After adding size of overhead etc, the final adjust
size can overflow and becomes very small , but a legal size.
This could lead to memory corruption. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* 64 bit platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* On 64 bit platform, when memory manager is asked to *
* allocatehuge size of memory, it does not check if the asked *
* 'size'istoo big. After adding size of overhead etc, the *
* final adjustsize can overflow and becomes very small , but a *
* legal size.This could lead to memory corruption. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 9.7 Fix Pack 3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version 9.7 Fix Pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.05.2010
27.09.2010
27.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
