[MDEV-35429] my_snprintf fixes for 10.5+ - Jira

Details

Type: Technical task
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.5
Fix Version/s: 10.5.28
Component/s: Storage Engine - InnoDB, Storage Engine - MyISAM
Labels:
- tech_debt

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.5 and up, the following strings may display their fields corrupted depending on the compiler and platform:

…,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>
…,<database>,,<event status>
…,<database>,<table>,
…,<database>,<table>|<new database>.<new table>,
…at offset <RegExp error offset>
The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.
The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>
<±><seconds>.<microseconds>
table->s->reclength <length> table->s->fields <count>
table->s->key_info[<index>] flags & HA_NOSAME = <integer>
table->field[<index>]->offset = %<difference> and the chunk that follows
repl.max_ws_size=<size>
~~InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]~~ (big-endian CPUs only)
Got error from move_object(<from> -> <to>): <error ID> % (% should be an error message)
normalized data truncated for multiple column index: … column-name: <<name>> data: <<data>> (known: Visual Studio)
Found block with wrong recordlength: <length> at <position>
Deleted block with impossible length <length> at <position>
Found block with wrong recordlength: <length> at <position>
[New] Found block with impossible length <length> at <position>; Skipped
Can't read indexpage from filepos: <integer>

Attachments

Activity

Ascending order - Click to sort in descending order

Jimmy Hú created issue - 2024-11-17 01:00

Jimmy Hú made changes - 2024-11-17 01:03

Field	Original Value	New Value
Status	Open [ 1 ]	In Progress [ 3 ]

Jimmy Hú made changes - 2024-11-17 01:03

Assignee	Jimmy Hú [ JIRAUSER55761 ]	Brandon Nesterenko [ JIRAUSER48702 ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Jimmy Hú made changes - 2024-11-17 01:05

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.5 and up, the following possibly publicly visible strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to?>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index: }}…{{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following possibly publicly visible strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to?>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú added a comment - 2024-11-17 01:06

https://github.com/MariaDB/server/pull/3485

Jimmy Hú added a comment - 2024-11-17 01:06 https://github.com/MariaDB/server/pull/3485

Jimmy Hú made changes - 2024-11-17 01:08

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.5 and up, the following possibly publicly visible strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to?>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following possibly publicly visible strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú made changes - 2024-11-17 20:01

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.5 and up, the following possibly publicly visible strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}
* debug messages that are not publicly visible

Jimmy Hú made changes - 2024-11-17 20:05

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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}
* debug messages that are not publicly visible

~~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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú made changes - 2024-11-17 20:51

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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580]) (missed in ~~MDEV-31340~~)
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú made changes - 2024-11-17 20:51

Link

This issue is caused by ~~MDEV-31340~~ [ ~~MDEV-31340~~ ]

Jimmy Hú made changes - 2024-11-17 20:53

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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580]) (missed in ~~MDEV-31340~~)
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580]) (missed in [{{fd247cc21f}}|https://github.com/MariaDB/server/commit/fd247cc21fbc975fbc7f20ef2c4e722f13552330] (~~MDEV-31340~~))
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú made changes - 2024-11-17 21:26

Priority

Minor [ 4 ]

Major [ 3 ]

Jimmy Hú made changes - 2024-11-17 22:52

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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580]) (missed in [{{fd247cc21f}}|https://github.com/MariaDB/server/commit/fd247cc21fbc975fbc7f20ef2c4e722f13552330] (~~MDEV-31340~~))
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú made changes - 2024-11-17 22:52

Link

This issue is caused by ~~MDEV-31340~~ [ ~~MDEV-31340~~ ]

Jimmy Hú made changes - 2024-11-17 23:30

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.5 and up, the following strings may display corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display their fields corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

Jimmy Hú added a comment - 2024-12-08 02:06

Hm? The PR’s merged to main already.
I’m not sure what more to put in the “Component/s” field though.

Jimmy Hú added a comment - 2024-12-08 02:06 Hm? The PR’s merged to main already. I’m not sure what more to put in the “Component/s” field though.

Jimmy Hú made changes - 2024-12-08 02:06

Component/s		Storage Engine - InnoDB [ 10129 ]
Component/s		Storage Engine - MyISAM [ 10600 ]
Fix Version/s		10.5.28 [ 29952 ]
Fix Version/s	10.5 [ 23123 ]
Resolution		Fixed [ 1 ]
Status	In Review [ 10002 ]	Closed [ 6 ]

Jimmy Hú made changes - 2025-01-10 22:54

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.5 and up, the following strings may display their fields corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Can't read indexpage from filepos: <integer>}}

~~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.5 and up, the following strings may display their fields corrupted depending on the compiler and platform:

* …{{,<server host>,<username>,<host>,<connection ID>,<query ID>,<operation>}}
* …{{,<database>,,<event status>}}
* …{{,<database>,<table>,}}
* …{{,<database>,<table>|<new database>.<new table>,}}
* …{{at offset <RegExp error offset>}}
* {{The slave is applying a ROW event on behalf of a<event> statement on table <table> and is currently taking a considerable amount of time (<difference> seconds). This is due to the fact that it is scanning <something> while looking up records to be processed.}}
* {{The current group of events starts with a non-GTID <type> event; the last seen GTID is <GTID>}}
* {{<±><seconds>.<microseconds>}}
* {{table->s->reclength <length>}} {{table->s->fields <count>}}
* {{table->s->key_info[<index>] flags & HA_NOSAME = <integer>}}
* {{table->field[<index>]->offset = %<difference>}} and the chunk that follows
* {{repl.max_ws_size=<size>}}
* -{{InnoDB: invalid PAGE_COMPRESSION_LEVEL = <level>. Valid values are [1, 2, 3, 4, 5, 6, 7, 8, 9]}}- (big-endian CPUs only)
* {{Got error from move_object(<from> -> <to>): <error ID> %}} ({{%}} should be an error message)
* {{normalized data truncated for multiple column index:}} … {{column-name: <<name>> data: <<data>>}} (known: [Visual Studio|https://github.com/MariaDB/server/pull/3360#discussion_r1712667580])
* {{Found block with wrong recordlength: <length> at <position>}}
* {{Deleted block with impossible length <length> at <position>}}
* {{Found block with wrong recordlength: <length> at <position>}}
* [New] {{Found block with impossible length <length> at <position>; Skipped}}
* {{Can't read indexpage from filepos: <integer>}}

People

Assignee:: Brandon Nesterenko

Reporter:: Jimmy Hú

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2024-11-17 01:00

Updated:: 2025-01-14 06:57

Resolved:: 2024-12-08 02:06

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Activity

People

Dates

Git Integration