From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: zlang@redhat.com, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] check: collect core dumps from systemd-coredump
Date: Tue, 21 Oct 2025 21:28:58 -0700 [thread overview]
Message-ID: <20251022042858.GL3356773@frogsfrogsfrogs> (raw)
In-Reply-To: <aPhcblEhs-8YXWkB@infradead.org>
On Tue, Oct 21, 2025 at 09:24:14PM -0700, Christoph Hellwig wrote:
> On Tue, Oct 21, 2025 at 11:42:35AM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > On modern RHEL (>=8) and Debian KDE systems, systemd-coredump can be
>
> Only KDE? Most of my test systems don't have any graphic
> environment set up.
Non-KDE Debian doesn't bother installing systemd-coredump. My actual
test systems have non-graphical Debian, but then I stood up one OL10
system for giggles and <kaboom> coredumps broke. :P
> Anyway, the changes looks fine:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Thanks!
--D
next prev parent reply other threads:[~2025-10-22 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:39 [PATCHSET 2/2] fstests: integrate with coredump capturing Darrick J. Wong
2025-10-21 18:42 ` [PATCH 1/2] fsstress: don't abort when stat(".") returns EIO Darrick J. Wong
2025-10-22 4:22 ` Christoph Hellwig
2025-10-21 18:42 ` [PATCH 2/2] check: collect core dumps from systemd-coredump Darrick J. Wong
2025-10-22 4:24 ` Christoph Hellwig
2025-10-22 4:28 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-29 20:08 [PATCHSET 3/3] fstests: integrate with coredump capturing Darrick J. Wong
2025-07-29 20:11 ` [PATCH 2/2] check: collect core dumps from systemd-coredump Darrick J. Wong
2025-08-02 13:47 ` Zorro Lang
2025-08-12 18:14 ` Darrick J. Wong
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=20251022042858.GL3356773@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.