[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG_fn=V3a-kLkjE252V4ncHWDR0YhMby7nd1P6RNQA4aPf+fRw@mail.gmail.com>
Date: Thu, 16 Feb 2023 17:34:33 +0100
From: Alexander Potapenko <glider@...gle.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: kasan-dev <kasan-dev@...glegroups.com>,
open list <linux-kernel@...r.kernel.org>,
kunit-dev@...glegroups.com, lkft-triage@...ts.linaro.org,
regressions@...ts.linux.dev, Marco Elver <elver@...gle.com>,
Anders Roxell <anders.roxell@...aro.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: next: x86_64: kunit test crashed and kernel panic
On Thu, Feb 16, 2023 at 1:13 PM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> Following kernel panic noticed while running KUNIT testing on qemu-x86_64
> with KASAN enabled kernel.
>
> CONFIG_KASAN=y
> CONFIG_KUNIT=y
> CONFIG_KUNIT_ALL_TESTS=y
>
This is reproducible for me locally, taking a look...
> <4>[ 38.796558] ? kmalloc_memmove_negative_size+0xeb/0x1f0
> <4>[ 38.797376] ? __pfx_kmalloc_memmove_negative_size+0x10/0x10
Most certainly kmalloc_memmove_negative_size() is related.
Looks like we fail to intercept the call to memmove() in this test,
passing -2 to the actual __memmove().
Powered by blists - more mailing lists