From: Peter Zijlstra <peterz@infradead.org>
To: Kees Cook <kees@kernel.org>
Cc: Alessandro Carminati <acarmina@redhat.com>,
linux-kselftest@vger.kernel.org,
Dan Carpenter <dan.carpenter@linaro.org>,
Daniel Diaz <daniel.diaz@linaro.org>,
David Gow <davidgow@google.com>,
Arthur Grillo <arthurgrillo@riseup.net>,
Brendan Higgins <brendan.higgins@linux.dev>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Maxime Ripard <mripard@kernel.org>,
Ville Syrjala <ville.syrjala@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>,
Guenter Roeck <linux@roeck-us.net>,
Alessandro Carminati <alessandro.carminati@gmail.com>,
Jani Nikula <jani.nikula@intel.com>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Linux Kernel Functional Testing <lkft@linaro.org>,
dri-devel@lists.freedesktop.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v5 1/5] bug/kunit: Core support for suppressing warning backtraces
Date: Mon, 2 Jun 2025 09:57:07 +0200 [thread overview]
Message-ID: <20250602075707.GI21197@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <8C5E309E-03E5-4353-8515-67A53EC6C9E3@kernel.org>
On Sat, May 31, 2025 at 06:51:50AM -0700, Kees Cook wrote:
> It's not for you, then. :) I can't operate ftrace, but I use kunit
> almost daily. Ignoring WARNs makes this much nicer, and especially for
> CIs.
I'm thinking you are more than capable of ignoring WARNs too. This
leaves the CI thing.
So all this is really about telling CIs which WARNs are to be ignored,
and which are not? Surely the easiest way to achieve that is by
printing more/better identifying information instead of suppressing
things?
next prev parent reply other threads:[~2025-06-02 7:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 13:27 [PATCH v5 0/5] kunit: Add support for suppressing warning backtraces Alessandro Carminati
2025-05-26 13:27 ` [PATCH v5 1/5] bug/kunit: Core " Alessandro Carminati
2025-05-28 22:47 ` Kees Cook
2025-05-29 9:02 ` Peter Zijlstra
2025-05-29 17:46 ` Kees Cook
2025-05-30 9:25 ` Peter Zijlstra
2025-05-29 9:01 ` Peter Zijlstra
2025-05-29 10:36 ` Alessandro Carminati
2025-05-30 14:01 ` Peter Zijlstra
2025-05-30 17:48 ` Kees Cook
2025-05-31 10:23 ` Peter Zijlstra
2025-05-31 13:51 ` Kees Cook
2025-06-02 7:57 ` Peter Zijlstra [this message]
2025-06-02 10:38 ` Maxime Ripard
2025-06-03 11:40 ` Simona Vetter
2025-06-02 11:13 ` Maxime Ripard
2025-06-03 12:26 ` Peter Zijlstra
2025-06-04 3:30 ` Daniel Latypov
2025-06-06 8:05 ` Maxime Ripard
2025-05-31 10:25 ` Peter Zijlstra
2025-05-31 7:46 ` Peter Zijlstra
2025-05-31 7:52 ` Alessandro Carminati
2025-05-30 9:26 ` Peter Zijlstra
2025-05-26 13:27 ` [PATCH v5 2/5] bug/kunit: Suppressing warning backtraces reduced impact on WARN*() sites Alessandro Carminati
2025-05-28 22:52 ` Kees Cook
2025-05-26 13:27 ` [PATCH v5 3/5] Add unit tests to verify that warning backtrace suppression works Alessandro Carminati
2025-05-26 13:27 ` [PATCH v5 4/5] drm: Suppress intentional warning backtraces in scaling unit tests Alessandro Carminati
2025-05-26 13:27 ` [PATCH v5 5/5] kunit: Add documentation for warning backtrace suppression API Alessandro Carminati
2025-06-02 7:24 ` [PATCH v5 0/5] kunit: Add support for suppressing warning backtraces Dan Carpenter
2025-06-02 10:47 ` Maxime Ripard
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=20250602075707.GI21197@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acarmina@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alessandro.carminati@gmail.com \
--cc=arthurgrillo@riseup.net \
--cc=brendan.higgins@linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=daniel.diaz@linaro.org \
--cc=daniel@ffwll.ch \
--cc=davidgow@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=skhan@linuxfoundation.org \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox