Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8390

innodb.innodb-flush-changed-page-bitmaps crashes

    Details

    • Sprint:
      10.1.6-2

      Description

      innodb.innodb-flush-changed-page-bitmaps test crashes. It started crashing immediately after it was introduced in

      commit b7ff2f1b59c42171ff50fc682e8f723f0713d688
      Author: Jan Lindström <jan.lindstrom@mariadb.com>
      Date:   Tue Jun 23 14:36:24 2015 +0300
      
          MDEV-7472: Implementation of user statements for handling the xtradb changed
          
          Introduce a new dummy INFORMATION_SCHEMA.CHANGED_PAGE_BITMAPS table to XtraD
          with reset_table callback to allow FLUSH NO_WRITE_TO_BINLOG CHANGED_PAGE_BIT
          to be called from innobackupex.
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            jplindst Jan Lindström added a comment -

            commit 4fac6269172eab2be0490a12936248113d14848d
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Mon Jun 29 12:48:42 2015 +0300

            MDEV-8390: innodb.innodb-flush-changed-page-bitmaps crashes

            Analysis: Flush changed page bitmaps calls log_online_follow_redo_log
            that later calls log_group_read_log_seg with release_mutex = true
            and that causes the log_sys mutex being released before
            log_decrypt_after_read function that later required log_sys mutex.

            Fix: Enter log_sys mutex before log_decrypt_after_read if mutex
            is released and release the mutex after the function if we
            acquired it before function call.

            Show
            jplindst Jan Lindström added a comment - commit 4fac6269172eab2be0490a12936248113d14848d Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Mon Jun 29 12:48:42 2015 +0300 MDEV-8390 : innodb.innodb-flush-changed-page-bitmaps crashes Analysis: Flush changed page bitmaps calls log_online_follow_redo_log that later calls log_group_read_log_seg with release_mutex = true and that causes the log_sys mutex being released before log_decrypt_after_read function that later required log_sys mutex. Fix: Enter log_sys mutex before log_decrypt_after_read if mutex is released and release the mutex after the function if we acquired it before function call.

              People

              • Assignee:
                jplindst Jan Lindström
                Reporter:
                serg Sergei Golubchik
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h

                    Agile