From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@kernel.org, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] check: capture dmesg of mount failures if test fails
Date: Tue, 14 Apr 2026 00:59:12 -0700 [thread overview]
Message-ID: <ad3z0FFzJqhIiqVQ@infradead.org> (raw)
In-Reply-To: <177610262444.115381.1847570200616394322.stgit@frogsfrogsfrogs>
On Mon, Apr 13, 2026 at 10:51:25AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Capture the kernel output after a mount failure occurs. If the test
> itself fails, then keep the logging output for further diagnosis.
I have to admit I don't really understand what the xunit and selftests
stuff is doing. Can you explain that a bit in the commit message?
next prev parent reply other threads:[~2026-04-14 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 17:50 [PATCHSET 2/2] fstests: capture logs from mount failures Darrick J. Wong
2026-04-13 17:51 ` [PATCH 1/2] treewide: convert all $MOUNT_PROG to _mount Darrick J. Wong
2026-04-14 7:58 ` Christoph Hellwig
2026-04-16 17:34 ` Zorro Lang
2026-04-16 17:56 ` Darrick J. Wong
2026-04-13 17:51 ` [PATCH 2/2] check: capture dmesg of mount failures if test fails Darrick J. Wong
2026-04-14 7:59 ` Christoph Hellwig [this message]
2026-04-14 17:17 ` Darrick J. Wong
2026-04-15 5:34 ` Christoph Hellwig
2026-04-16 17:56 ` Zorro Lang
2026-04-16 18:57 ` Darrick J. Wong
2026-04-16 19:15 ` [PATCH v1.1 " Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2024-12-31 23:35 [PATCHSET 3/5] fstests: capture logs from mount failures Darrick J. Wong
2024-12-31 23:56 ` [PATCH 2/2] check: capture dmesg of mount failures if test fails Darrick J. Wong
2025-01-06 11:18 ` Nirjhar Roy
2025-01-06 23:52 ` Darrick J. Wong
2025-01-13 5:55 ` Nirjhar Roy
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=ad3z0FFzJqhIiqVQ@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@kernel.org \
/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