Bug #106081 Missed init of m_nodes in fix_nodegroup

Submitted: 6 Jan 2022 11:44 Modified: 18 Nov 2022 17:57
Reporter: Mikael Ronström Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:8.0.27 OS:Any
Assigned to: CPU Architecture:Any

[6 Jan 2022 11:44] Mikael Ronström 
Description:
The array m_nodes set in fix_nodegroup for each bucket is not fully initialised.
This can lead to crash when uninitialised memory is used when no node exists for
a bucket. This leads to a crash instead of a missing node.

How to repeat:
Rare occurrence when running autotest.
Probably need an ERROR insert to reproduce by initing memory to bad values.

Suggested fix:
Init array to 0 before loop that sets the values.
[18 Jan 2022 12:34] MySQL Verification Team 
Hi Mikael,

Thanks for the report
all best
Bogdan
[18 Nov 2022 17:57] Jon Stephens 
Documented fix as follows in the NDB 7.5.29, 7.6.25, and 8.0.32 changelogs:

    Fixed an uninitialized variable in Suma.cpp.

Closed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.