Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
pool->threads is freed before being reassigned the new pool.
Although not really a memory barrier I though it prudent to keep the pool thread count to be the lower of the old/new thread list before the new threads is allocated.
Patch refers
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Kristian Nielsen [ knielsen ] |
Summary | parallel threads resizing - potential race condition to access freed memory | [PATCH] parallel threads resizing - potential race condition to access freed memory |
Fix Version/s | 10.1 [ 16100 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 10.1.3 [ 18000 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v2 [ 58721 ] | MariaDB v3 [ 64822 ] |
Workflow | MariaDB v3 [ 64822 ] | MariaDB v4 [ 132469 ] |
Hm. As you say, due to no barriers this doesn't actually make any semantic
change. But ok, if you think it makes the code clearer, it doesn't hurt
anything, so I'll push it to 10.1.