From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/1] kill11: Skip pipe-based core dumps per signal
Date: Tue, 14 Jul 2026 10:43:00 +0200 [thread overview]
Message-ID: <alX2lMoWc2tdNut0@yuki.lan> (raw)
In-Reply-To: <6a510c80.fc4d87c3.115da4.55fa@mx.google.com>
Hi!
> > Thinking of it once more, I wonder what exactly fails in the
> > systemd-coredump case. I guess that it may delay the test execution a
> > bit but the crashed process should eventualy quit and the test wait()
> > call should collect it. If that wasn't the case systemd-coredump would
> > break one of the fundamentals of UNIX process management.
>
> Let's forget about systemd for a second.
>
> The problem is that by using `pause()` that is not draining the buffer we
> never ends the piped user-space helper. The default behaviour for a piped
> helper is that kernel collect the coredump until helper drains the pipe.
Which would mean that the system this is failing on is mis-configured at
best. I've tested this on Leap 16.0 that uses systemd-coredump and
everything works fine there.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-14 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 10:28 [LTP] [PATCH v2 1/1] kill11: Skip pipe-based core dumps per signal Jan Polensky
2026-07-09 13:53 ` [LTP] " linuxtestproject.agent
2026-07-09 17:38 ` [LTP] [PATCH v2 1/1] " Andrea Cervesato via ltp
2026-07-10 12:27 ` Cyril Hrubis
2026-07-10 12:41 ` Andrea Cervesato via ltp
2026-07-10 12:45 ` Cyril Hrubis
2026-07-10 12:55 ` Andrea Cervesato via ltp
2026-07-10 13:04 ` Cyril Hrubis
2026-07-10 15:15 ` Andrea Cervesato via ltp
2026-07-14 8:43 ` Cyril Hrubis [this message]
2026-07-10 17:58 ` Jan Polensky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alX2lMoWc2tdNut0@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox