[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+fCnZeSq0E0SoDOWAEs=ZTYFDZnT2Ox1X5CG1gQC0i88n8WQQ@mail.gmail.com>
Date: Sat, 18 May 2024 00:53:55 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: Nico Pache <npache@...hat.com>
Cc: andrey.konovalov@...ux.dev, Marco Elver <elver@...gle.com>,
Alexander Potapenko <glider@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>, kasan-dev@...glegroups.com,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
Erhard Furtner <erhard_f@...lbox.org>, Daniel Axtens <dja@...ens.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kasan, fortify: properly rename memintrinsics
On Fri, May 17, 2024 at 9:50 PM Nico Pache <npache@...hat.com> wrote:
>
> Thank you for fixing this !! The test no longer panics :)
Awesome, thank you for testing!
> Now that the test progresses I also see rcu_uaf failing.
> # rcu_uaf: EXPECTATION FAILED at mm/kasan/kasan_test.c:870
> KASAN failure expected in "call_rcu(&global_rcu_ptr->rcu,
> rcu_uaf_reclaim); rcu_barrier()", but none occurred
> not ok 31 rcu_uaf
> I can open a new thread for that if you'd like.
Looks like something else is broken :(
Unfortunately, I failed to boot a kernel built with the config that
you provided in QEMU.
If you can provide a config that boots in QEMU or instructions on how
to reproduce the issue, I can take a look.
Thanks!
Powered by blists - more mailing lists