This bug was fixed in the package isc-kea - 2.4.1-3build1
---
isc-kea (2.4.1-3build1) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
18:32:35 +
** Changed in: isc-kea (Ubuntu)
Status: Fix Committed => Fix Released
** C
** Changed in: isc-kea (Ubuntu)
Milestone: None => ubuntu-24.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055151
Title:
kea-ctrl-agent segfault in ppc64el dep8 test
To manage notifica
Synced https://launchpad.net/debian/+source/isc-kea/2.4.1-3 from debian
to fix this.
** Changed in: isc-kea (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Thanks Sergio for thinking of LTO!
I opened:
https://salsa.debian.org/debian/isc-kea/-/merge_requests/54
We can't check from the CI logs that it actually disables LTO, but the
diff _really_ seems right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
After some more debugging/testing, it seems like the problem is indeed
caused by compiler optimization. More specifically, LTO. Disabling it
seems to have done the trick, and I can't reproduce the segmentation
fault anymore.
Basically:
ifeq ($(DEB_HOST_ARCH),ppc64el)
export DEB_BUILD_MAINT_OPTI
I think a build with an older boost worked:
--- a/debian/control
+++ b/debian/control
@@ -19,8 +19,8 @@ Build-Depends:
docbook-xsl,
elinks,
flex,
- libboost-dev,
- libboost-system-dev,
+ libboost1.74-dev,
+ libboost-system1.74-dev,
liblog4cplus-dev,
libpq-dev,
libssl-dev,
Locally I do
When using the shutdown command via the API, kea-ctrl-agent does not
segfault:
# kea-shell --auth-user kea-api --auth-password $(cat
/etc/kea/kea-api-password) --host localhost shutdown
[ { "result": 0, "text": "Control Agent is shutting down" } ]
I had the server running inside gdb:
(...)
DEBUG
A rebuild of the package in noble release (not proposed) currently also
segfaults in ppc64el :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055151
Title:
kea-ctrl-agent segfault in ppc64el dep8 t
Sorry, wrong analysis, the rebuild is still segfaulting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055151
Title:
kea-ctrl-agent segfault in ppc64el dep8 test
To manage notifications about this
I had a ppc64el machine where I reproduced this segfault before. I just
logged in again, updated the environment to latest noble proposed, and
did a new rebuild. Those new binaries didn't segfault anymore.
I'm now doing a "proper" build in a ppa, and will run the DEP8 tests
there (or locally, if t
I'm looking at this again.
** Changed in: isc-kea (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055151
Title:
kea-ctrl-agent segfault in ppc64el dep8
** Tags added: server-todo
** Changed in: isc-kea (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: isc-kea (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Attachment added: "build-with-noble-proposed-crashed.log"
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/2055151/+attachment/5751226/+files/build-with-noble-proposed-crashed.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "build-noble-release-worked.log"
https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/2055151/+attachment/5751225/+files/build-noble-release-worked.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
A rebuild of 2.4.1-1 with noble release produced binaries that worked.
A rebuild of the same 2.4.1-1 with noble-proposed produced binaries that
crashed on shutdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
We were able to reproduce this with the -2 build, but not the -1 one. A
simple "dpkg-reconfigure kea-ctrl-agent" on ppc64el crashes with a
segfault:
[Fri Mar 1 13:34:41 2024] kea-ctrl-agent[6366]: segfault (11) at 0 nip
63821b5fbafc lr 63821b5fbad8 code 1 in
libkea-asiolink.so.56.0.0[63821b5d00
The other daemons are also crashin, and it's on shutdown. Either via
systemctl stop, or even starting them in the foreground and just hitting
ctrl-c, they segfault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Maybe boost related? Anyway, caught this backtrace:
(gdb) r -c /etc/kea/kea-ctrl-agent.conf
Starting program: /usr/sbin/kea-ctrl-agent -c /etc/kea/kea-ctrl-agent.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".
[New T
> which is maybe a side effect of the crash?
Yeah, it's what I thought, who knows what jq got in stdin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055151
Title:
kea-ctrl-agent segfault in ppc6
I also happened to notice:
474s ++ jq -r '.[0].text'
475s jq: parse error: Invalid numeric literal at line 1, column 7
which is maybe a side effect of the crash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
20 matches
Mail list logo
