[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <81d3f794-a19b-4b62-8c21-7c6ef9acb552@moroto.mountain>
Date: Tue, 4 Jun 2024 11:21:34 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>, kunit-dev@...glegroups.com,
lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>, smayhew@...hat.com,
David Gow <davidgow@...gle.com>, Rae Moar <rmoar@...gle.com>,
Ivan Orlov <ivan.orlov0322@...il.com>, npache@...hat.com,
Arnd Bergmann <arnd@...db.de>
Subject: Re: kunit_test: KASAN: null-ptr-deref in range -
kunit_generic_run_threadfn_adapter on qemu_arm64
On Mon, Jun 03, 2024 at 07:39:24PM +0530, Naresh Kamboju wrote:
> The following kernel null pointer dereference is noticed on qemu-arm64
> while running
> kunit tests with the Linux next-20240603 tag kernel.
>
> This is always reproducible and the system is stable after this.
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
These are intentional... The function name just changed so it's showing
up as a new bug. I tried to add a big printk before this NULL
dereference but the printk message never showed up in dmesg...
+ kunit_info(test, "Testing that a NULL dereference causes a test failure\n");
+ kunit_info(test, "*** This will lead to an intentional stack trace ***\n");
regards,
dan carpenter
Powered by blists - more mailing lists