Bug #106128 | Can't view bug 105715 | ||
---|---|---|---|
Submitted: | 10 Jan 2022 17:04 | Modified: | 11 Jan 2022 16:24 |
Reporter: | Christos Chatzaras | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Websites: bugs.mysql.com | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[10 Jan 2022 17:04]
Christos Chatzaras
[10 Jan 2022 17:05]
Christos Chatzaras
EDIT: Fix title.
[10 Jan 2022 18:40]
Valeriy Kravchuk
Probably because https://bugs.mysql.com/bug.php?id=105715 was made private, because it was considered as a "security issue", or just because somebody could do it and did it. Usually there is no way back no matter if it's fixed or what was the reason...
[11 Jan 2022 5:49]
MySQL Verification Team
Hello Christos Chatzaras, Thank you for the feedback. As Valeriy rightly said, Bug #105715 is marked as a private and thus you are not able to view. Good news is that Bug #105715 is no longer reproducible on upcoming release. Fixed in the upcoming 8.0.28 under the heading of Bug#33570629 [InnoDB] MySQL Server crash - assertion failure: ddl0builder.cc:1495:n >= IO_BLOCK_SIZE Once 8.0.28 is released then details would appear in the appropriate change log i.e. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-28.html regards, Umesh
[11 Jan 2022 16:23]
Christos Chatzaras
Can you please send me the patch so I can add it to 5.8.27 ?
[11 Jan 2022 16:24]
Christos Chatzaras
I mean to add it to 8.0.27