Merge ~ahasenack/ubuntu/+source/mariadb-10.6:kinetic-mariadb-uring-memlock into ubuntu/+source/mariadb-10.6:ubuntu/devel
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 7cc6a5fd0943aa147c93f5527415ee715d12f5ff | ||||
Proposed branch: | ~ahasenack/ubuntu/+source/mariadb-10.6:kinetic-mariadb-uring-memlock | ||||
Merge into: | ubuntu/+source/mariadb-10.6:ubuntu/devel | ||||
Diff against target: |
43 lines (+12/-1) 3 files modified
debian/changelog (+6/-0) debian/control (+2/-1) debian/rules (+4/-0) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergio Durigan Junior (community) | Approve | ||
Canonical Server | Pending | ||
Review via email: mp+420845@code.launchpad.net |
Description of the change
Disable lto to fix catching the exception that is thrown when mariadb tries to setup uring and it can't lock enough memory due to a low MEMLOCK limit.
For some reason, the exception isn't caught when lto is enabled, and mariadb crashes with sigabort instead. Upstream is wondering if it's a compiler bug.
Normally universe packages get this fix via an added entry in the lto-disabled-
I still have to write up the SRU template, and create jammy packages. PPAs are unusable atm.
PPA at https:/
To test the existence of the bug, these steps are sufficient:
- create a focal VM
- confirm ulimit -l value in that VM. I've been getting the value "64", but anything lower than 256 will trigger the bug.
- inside that VM, create a jammy LXD
- iside that LXD, install mariadb-server. It will fail.
The mariadb build takes a long time. With 12 cores, about 1h, so I suggest to wait for the ppa. Or not :)
I'm unsure what the jammy SRU version will be. Current state is:
mariadb-10.6 | 1:10.6.7-2ubuntu1 | jammy/universe | source
mariadb-10.6 | 1:10.6.7-2ubuntu1 | kinetic/universe | source
mariadb-10.6 | 1:10.6.7-3 | jammy-proposed/
mariadb-10.6 | 1:10.6.7-3 | kinetic-
I don't know if the 10.6.7-3 jammy-proposed upload will be removed. I'll ask around.
Thanks, Andreas.
This makes sense to me, and I agree with the workaround. Unfortunately these LTO bugs are very hard to diagnose... Daniel Black did a good job investigating it.
Regarding the version, I think 1:10.6.7-3 has been removed from jammy-proposed because I don't see it there anymore. So your upload should be versioned 1:10.6. 7-2ubuntu1. 1.
LGTM with this change.