1
0
mirror of https://github.com/MariaDB/server.git synced 2025-11-27 05:41:41 +03:00
Files
mariadb/mysql-test/suite/innodb/r
Vlad Lesin b54e7b0cea MDEV-31185 rw_trx_hash_t::find() unpins pins too early
rw_trx_hash_t::find() acquires element->mutex, then unpins pins, used for
lf_hash element search. After that the "element" can be deallocated and
reused by some other thread.

If we take a look rw_trx_hash_t::insert()->lf_hash_insert()->lf_alloc_new()
calls, we will not find any element->mutex acquisition, as it was not
initialized yet before it's allocation. rw_trx_hash_t::insert() can reuse
the chunk, unpinned in rw_trx_hash_t::find().

The scenario is the following:

1. Thread 1 have just executed lf_hash_search() in
rw_trx_hash_t::find(), but have not acquired element->mutex yet.
2. Thread 2 have removed the element from hash table with
rw_trx_hash_t::erase() call.
3. Thread 1 acquired element->mutex and unpinned pin 2 pin with
lf_hash_search_unpin(pins) call.
4. Some thread purged memory of the element.
5. Thread 3 reused the memory for the element, filled element->id,
element->trx.
6. Thread 1 crashes with failed "DBUG_ASSERT(trx_id == trx->id)"
assertion.

Note that trx_t objects are also reused, see the code around trx_pools
for details.

The fix is to invoke "lf_hash_search_unpin(pins);" after element->trx is
stored in local variable in rw_trx_hash_t::find().

Reviewed by: Nikita Malyavin, Marko Mäkelä.
2023-05-19 15:50:20 +03:00
..
2020-05-05 20:33:10 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2019-07-22 15:28:05 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2019-11-19 01:32:50 +02:00
2022-09-13 16:36:38 +03:00
2019-08-21 15:23:45 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-10-11 15:18:49 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2019-08-21 15:23:45 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-12-13 11:37:33 +02:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2021-12-25 12:13:03 +01:00
2023-01-03 16:10:02 +02:00
2020-07-31 13:51:28 +03:00
2022-10-05 20:30:57 +03:00
2022-12-13 11:37:33 +02:00
2022-06-27 10:14:37 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2022-09-13 16:36:38 +03:00
2020-09-22 14:33:03 +03:00
2022-03-15 08:10:35 +02:00
2020-04-16 12:12:26 +03:00
2020-06-05 18:05:22 +03:00