Bug#1103296: systemd: Caught <ABRT> from our own process

[Peter Palfrader]

On Wed, 21 May 2025, Luca Boccassi wrote:

> On Tue, 22 Apr 2025 06:13:48 +0000 Peter Palfrader <weasel at debian.org>
> wrote:
> > On Wed, 16 Apr 2025, Luca Boccassi wrote:
> > 
> > > Control: tags -1 moreinfo
> > > 
> > > I see there are 3 threads in the full backtrace. In the version in
> > > bookworm there was still an async cleanup routine that used posix
> > > threads. This is known to mix really badly with glibc's handling of
> > > malloc internals, so I strongly suspect that's the issue. This was
> > > replaced with using subprocesses in trixie.
> > > 
> > > Are you able to reproduce the issue with stable-backports or
> > > testing/unstable?
> > 
> > We switched the unit file to a static user (nobody), which seems to
> have
> > been successful at triggering this issue.  I'll see if I can
> reproduce
> > the bug on a less-critical system and then try with a newer systemd.
> > I'll report back in either case.
> 
> It's been a month, any update?

I've tried several times to reproduce this on a test system.  However,
the test system is VMs, while the production system is hardware.

So far, no luck.


Unfortunately, testing on the production system is close to infeasible.
I might have one more thing I can try, but don't block on that.

Cheers,
weasel
-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/