From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [PATCH 0/2] of: unittest: option to allow tests that trigger kernel stack dump
Date: Tue, 28 Feb 2023 19:21:14 -0600 [thread overview]
Message-ID: <20230301012116.1488132-1-frowand.list@gmail.com> (raw)
Commit 74df14cd301a ("of: unittest: add node lifecycle tests") added
some tests that trigger a kernel stack dump. Filtering the boot
messages with scripts/dtc/of_unittest_expect detects that the stack
dump is expected instead of being a test error.
Test beds might interpret the stack dumps as errors, resulting in
needless debugging and error reports. These test beds are likely
to remove unittests due to these stack dumps. To avoid these problems,
have the unittest default to skip the tests that trigger a stack dump.
Add a kernel cmdline option to not skip those tests. This option can
be used by testers who are able to interpret the stack dumps as not
an error.
Frank Rowand (2):
of: unittest: option to allow tests that trigger kernel stack dump
of: unittest: add of_unittest_stackdump to kernel documentation
.../admin-guide/kernel-parameters.txt | 4 ++
drivers/of/unittest.c | 54 +++++++++++++++++--
2 files changed, 55 insertions(+), 3 deletions(-)
--
Frank Rowand <frowand.list@gmail.com>
next reply other threads:[~2023-03-01 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 1:21 Frank Rowand [this message]
2023-03-01 1:21 ` [PATCH 1/2] of: unittest: option to allow tests that trigger kernel stack dump Frank Rowand
2023-03-01 4:07 ` Guenter Roeck
2023-03-01 16:01 ` Frank Rowand
2023-03-24 21:43 ` Rob Herring
2023-03-26 0:56 ` Frank Rowand
2023-03-01 1:21 ` [PATCH 2/2] of: unittest: add of_unittest_stackdump to kernel documentation Frank Rowand
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=20230301012116.1488132-1-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).