Details
-
Technical task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6
Description
MDEV-21978 found many erroneous my_snprintf formattings when it reenabled GCC printf checks.
Patches to these errors should apply to the oldest applicable version in maintenance and up.
In MariaDB 10.6 and up, the following strings may display their fields corrupted depending on the compiler and platform:
- (DBUG) print_admin_msg: <name>, <Op. name>, <type>, <message> (Op. name and <type> print incorrectly)
- (DBUG) xid: <undefined> xid (<undefined> not filled in with xid)
- InnoDB: Index root page <ID> in <name> is corrupted at <undefined> (<undefined> not filled in with the offset) (from
MDEV-13542) - InnoDB: Failed to load tablespace <ID> for table <name>
(DBUG) Files : <count>(big-endian CPUs only?)- and
MDEV-34799
Attachments
Issue Links
- causes
-
MDEV-35478 Correction for table->space_id in dict_load_tablespace() was mistakenly applied on an earlier branch
-
- Closed
-
- is caused by
-
MDEV-13542 Crashing on a corrupted page is unhelpful
-
- Closed
-
- split to
-
MDEV-34799 "Could not write packet" err message args off by 1
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Jimmy Hú [ JIRAUSER55761 ] | |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Description |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with an offset) * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * debug messages that are not publicly visible |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <name>, <type>, <message>}} ({{<type>}} may print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Description |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <name>, <type>, <message>}} ({{<type>}} may print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <name>, <type>, <message>}} ({{<type>}} may print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Link |
This issue is caused by |
Description |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <name>, <type>, <message>}} ({{<type>}} may print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <Op. name>, <type>, <message>}} ({{Op. name}} and {{<type>}} print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Link |
This issue split to |
Description |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <Op. name>, <type>, <message>}} ({{Op. name}} and {{<type>}} print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?) |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <Op. name>, <type>, <message>}} ({{Op. name}} and {{<type>}} print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * -(DBUG) {{Files : <count>}}- (big-endian CPUs only?) * and |
Component/s | Storage Engine - InnoDB [ 10129 ] |
Description |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <Op. name>, <type>, <message>}} ({{Op. name}} and {{<type>}} print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * -(DBUG) {{Files : <count>}}- (big-endian CPUs only?) * and |
Patches to these errors should apply to the oldest applicable version in maintenance and up. In MariaDB 10.6 and up, the following strings may display their fields corrupted depending on the compiler and platform: * (DBUG) {{print_admin_msg: <name>, <Op. name>, <type>, <message>}} ({{Op. name}} and {{<type>}} print incorrectly) * (DBUG) {{xid: <undefined> xid}} ({{<undefined>}} not filled in with {{xid}}) * {{InnoDB: Index root page <ID> in <name> is corrupted at <undefined>}} ({{<undefined>}} not filled in with the offset) (from * {{InnoDB: Failed to load tablespace <ID> for table <name>}} * -(DBUG) {{Files : <count>}}- (big-endian CPUs only?) * and |
Fix Version/s | 10.6.21 [ 29953 ] | |
Fix Version/s | 10.6 [ 24028 ] | |
Assignee | Daniel Black [ danblack ] | |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10002 ] | Closed [ 6 ] |
Link |
This issue causes |