[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250328.sah9oog5ahSh@digikod.net>
Date: Fri, 28 Mar 2025 11:38:23 +0100
From: Mickaël Salaün <mic@...ikod.net>
To: Maxime Ripard <mripard@...nel.org>
Cc: Kees Cook <kees@...nel.org>,
Alessandro Carminati <acarmina@...hat.com>, linux-kselftest@...r.kernel.org,
David Airlie <airlied@...il.com>, Arnd Bergmann <arnd@...db.de>,
Maíra Canal <mcanal@...lia.com>, Dan Carpenter <dan.carpenter@...aro.org>,
Daniel Diaz <daniel.diaz@...aro.org>, David Gow <davidgow@...gle.com>,
Arthur Grillo <arthurgrillo@...eup.net>, Brendan Higgins <brendan.higgins@...ux.dev>,
Naresh Kamboju <naresh.kamboju@...aro.org>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>, Ville Syrjälä <ville.syrjala@...ux.intel.com>,
Daniel Vetter <daniel@...ll.ch>, Thomas Zimmermann <tzimmermann@...e.de>,
Guenter Roeck <linux@...ck-us.net>, Alessandro Carminati <alessandro.carminati@...il.com>,
Jani Nikula <jani.nikula@...el.com>, dri-devel@...ts.freedesktop.org, kunit-dev@...glegroups.com,
linux-arch@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
loongarch@...ts.linux.dev, x86@...nel.org
Subject: Re: [PATCH v4 00/14] Add support for suppressing warning backtraces
On Thu, Mar 13, 2025 at 06:24:25PM +0100, Maxime Ripard wrote:
> Hi,
>
> On Thu, Mar 13, 2025 at 10:17:49AM -0700, Kees Cook wrote:
> > On Thu, Mar 13, 2025 at 11:43:15AM +0000, Alessandro Carminati wrote:
> > > Some unit tests intentionally trigger warning backtraces by passing bad
> > > parameters to kernel API functions. Such unit tests typically check the
> > > return value from such calls, not the existence of the warning backtrace.
> >
> > Thanks for picking this series back up! I honestly thought this had
> > already landed. :)
> >
> > > With CONFIG_KUNIT enabled, image size increase with this series applied is
> > > approximately 1%. The image size increase (and with it the functionality
> > > introduced by this series) can be avoided by disabling
> > > CONFIG_KUNIT_SUPPRESS_BACKTRACE.
> >
> > Yeah, as with my prior review, I'm a fan of this. It makes a bunch of my
> > very noisy tests much easier to deal with.
>
> And for the record, we're also affected by this in DRM and would very
> much like to get it merged in one shape or another.
Here is another case:
https://lore.kernel.org/all/20250328.Ahc0thi6CaiJ@digikod.net/
It would be very useful to have this feature merged. Without it, we may
need to remove useful tests.
Powered by blists - more mailing lists