From: Andrey Konovalov <andreyknvl@gmail.com>
To: Nico Pache <npache@redhat.com>
Cc: andrey.konovalov@linux.dev, Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
kasan-dev@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Erhard Furtner <erhard_f@mailbox.org>,
Daniel Axtens <dja@axtens.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan, fortify: properly rename memintrinsics
Date: Sat, 18 May 2024 00:53:55 +0200 [thread overview]
Message-ID: <CA+fCnZeSq0E0SoDOWAEs=ZTYFDZnT2Ox1X5CG1gQC0i88n8WQQ@mail.gmail.com> (raw)
In-Reply-To: <CAA1CXcAdG=OFkBzjPqr7M_kC7VZUdj-+vH_2W4UidfbQwfQbeA@mail.gmail.com>
On Fri, May 17, 2024 at 9:50 PM Nico Pache <npache@redhat.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!
prev parent reply other threads:[~2024-05-17 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:01 andrey.konovalov
2024-05-17 15:21 ` Marco Elver
2024-05-17 19:50 ` Nico Pache
2024-05-17 22:53 ` Andrey Konovalov [this message]
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='CA+fCnZeSq0E0SoDOWAEs=ZTYFDZnT2Ox1X5CG1gQC0i88n8WQQ@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrey.konovalov@linux.dev \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=erhard_f@mailbox.org \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=ryabinin.a.a@gmail.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