Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-195

maxscaled.c ineffective DCB disposal

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.1.1
    • 1.3.0
    • Core
    • None
    • All

    Description

      The function maxscaled_accept makes two calls to dcb_add_to_zombieslist. The first will be ineffective - if debug is enabled the system will crash, otherwise it will do nothing but the DCB will be left allocated. The reason for this is that on creation the state of a DCB is DCB_STATE_ALLOCATED but the function dcb_add_to_zombieslist will only process a DCB that is in the state DCB_STATE_NOPOLLING. What will happen on the second call is more obscure. However, it would be preferable for there to be a single DCB disposal function available from outside dcb.c that makes its own decisions on how to deal with a DCB in any state.

      There are similar problems with telnetd.c

      Attachments

        Activity

          People

            martin brampton martin brampton (Inactive)
            martin brampton martin brampton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.