diff options
| author | unknown <davi@endora.local> | 2007-11-22 10:18:19 -0200 |
|---|---|---|
| committer | unknown <davi@endora.local> | 2007-11-22 10:18:19 -0200 |
| commit | 719e64e4a55a6893b14464cb28e8beaaa33f6a7c (patch) | |
| tree | 1f1004e1f043e7abf2b7ea25947a3f167bd05e2d /regex | |
| parent | 2aa5037c7ac3d94e16c310760ffa4b04ccdcc871 (diff) | |
| download | mariadb-git-719e64e4a55a6893b14464cb28e8beaaa33f6a7c.tar.gz | |
Bug#32528 Global read lock with a low priority write lock causes a server crash
FLUSH TABLES WITH READ LOCK fails to properly detect write locked
tables when running under low priority updates.
The problem is that when trying to aspire a global read lock, the
reload_acl_and_cache() function fails to properly check if the thread
has a low priority write lock, which later my cause a server crash or
deadlock.
The solution is to simple check if the thread has any type of the
possible exclusive write locks.
mysql-test/r/flush.result:
Add test case result for Bug#32528
mysql-test/t/flush.test:
Add test case for Bug#32528
sql/sql_parse.cc:
Although it should not matter under LOCK TABLES, use TL_WRITE_ALLOW_WRITE
to emphasize that it should fail in case of any write lock.
Diffstat (limited to 'regex')
0 files changed, 0 insertions, 0 deletions