Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21978 make my_vsnprintf to use gcc-compatible format extensions
  3. MDEV-35430

my_snprintf fixes for 10.6+

Details

    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

          Technical task - A technical task. MDEV-35478 Correction for table->space_id in dict_load_tablespace() was mistakenly applied on an earlier branch

          • Major - Major loss of function.
          • Closed
          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13542 Crashing on a corrupted page is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          split to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34799 "Could not write packet" err message args off by 1

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            ParadoxV5 Jimmy Hú created issue -
            ParadoxV5 Jimmy Hú made changes -
            Field Original Value New Value
            Status Open [ 1 ] In Progress [ 3 ]
            ParadoxV5 Jimmy Hú added a comment -

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

            ParadoxV5 Jimmy Hú added a comment - https://github.com/MariaDB/server/pull/3493
            ParadoxV5 Jimmy Hú made changes -
            Assignee Jimmy Hú [ JIRAUSER55761 ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            ParadoxV5 Jimmy Hú made changes -
            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 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             		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 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?)
            ParadoxV5 Jimmy Hú made changes -
            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 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?)             		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 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 MDEV-13542)
            * {{InnoDB: Failed to load tablespace <ID> for table <name>}}
            * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?)
            ParadoxV5 Jimmy Hú made changes -
            ParadoxV5 Jimmy Hú made changes -
            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 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 MDEV-13542)
            * {{InnoDB: Failed to load tablespace <ID> for table <name>}}
            * ~~(DBUG) {{Files : <count>}}~~ (big-endian CPUs only?)             		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 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?)
            ParadoxV5 Jimmy Hú made changes -
            ParadoxV5 Jimmy Hú made changes -
            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 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?)             		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 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
            ParadoxV5 Jimmy Hú made changes -
            Component/s Storage Engine - InnoDB [ 10129 ]
            ParadoxV5 Jimmy Hú made changes -
            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 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             		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
            danblack Daniel Black made changes -
            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 ]
            ParadoxV5 Jimmy Hú made changes -

            People

              danblack Daniel Black
              ParadoxV5 Jimmy Hú
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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