[MDEV-20399] SEGV in fil_system_t::keyrotate_next , InnoDB, table encrypted Created: 2019-08-21 Updated: 2022-02-10 Resolved: 2020-08-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5 |
| Fix Version/s: | 10.2.35, 10.3.26, 10.4.16, 10.5.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Matthias Leich | Assignee: | Marko Mäkelä |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | need_rr, not-10.1 | ||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Roel Van de Paar [ 2020-06-02 ] | ||||||||||||||||||||
|
Leads to:
Bug confirmed present in: Bug confirmed not present in: | ||||||||||||||||||||
| Comment by Marko Mäkelä [ 2020-08-08 ] | ||||||||||||||||||||
|
I think that in order to fix | ||||||||||||||||||||
| Comment by Marko Mäkelä [ 2020-08-10 ] | ||||||||||||||||||||
|
In Roel, mleich, is the SIGSEGV still repeatable with the
I suppose that Roel’s crash might be repeatable, because that SIGSEGV occurred in
apparently when dereferencing it. So far, I have pushed the | ||||||||||||||||||||
| Comment by Marko Mäkelä [ 2020-08-10 ] | ||||||||||||||||||||
|
I have merged the | ||||||||||||||||||||
| Comment by Roel Van de Paar [ 2020-08-11 ] | ||||||||||||||||||||
|
Testcase with SLEEP in comment 2020-06-02 is still repeatable.
| ||||||||||||||||||||
| Comment by Marko Mäkelä [ 2020-08-12 ] | ||||||||||||||||||||
|
I believe that both causes of this crash were fixed in |