From: Andrey Konovalov <andreyknvl@gmail.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Andrey Konovalov <andreyknvl@google.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Marco Elver <elver@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Oscar Salvador <osalvador@suse.de>,
Vlastimil Babka <vbabka@suse.cz>,
kasan-dev@googlegroups.com
Subject: Re: [linux-next:master] [kasan] 0e8b630f30: BUG_kmem_cache_node(Tainted:G_T):Poison_overwritten
Date: Thu, 23 Nov 2023 17:04:39 +0100 [thread overview]
Message-ID: <CA+fCnZd2JKZP43UJLciKOx2pRVwWDEUJZ0ik_BYC5atnwUGSfg@mail.gmail.com> (raw)
In-Reply-To: <202311231356.1e1fb71f-oliver.sang@intel.com>
On Thu, Nov 23, 2023 at 7:19 AM kernel test robot <oliver.sang@intel.com> wrote:
>
> kernel test robot noticed "BUG_kmem_cache_node(Tainted:G_T):Poison_overwritten" on:
>
> commit: 0e8b630f3053f0ff84b7c3ab8ff98a7393863824 ("kasan: use stack_depot_put for Generic mode")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 07b677953b9dca02928be323e2db853511305fa9]
>
> in testcase: boot
>
> compiler: clang-16
> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
> +--------------------------------------------------------------+------------+------------+
> | | 882f84db75 | 0e8b630f30 |
> +--------------------------------------------------------------+------------+------------+
> | BUG_kmem_cache_node(Tainted:G_T):Poison_overwritten | 0 | 55 |
> | BUG_kmem_cache_node(Tainted:G_B_T):Poison_overwritten | 0 | 55 |
> +--------------------------------------------------------------+------------+------------+
This should be fixed by "slub, kasan: improve interaction of KASAN and
slub_debug poisoning" and the most recent version of "kasan: Improve
free meta storage in Generic KASAN".
prev parent reply other threads:[~2023-11-23 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 6:19 kernel test robot
2023-11-23 16:04 ` 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+fCnZd2JKZP43UJLciKOx2pRVwWDEUJZ0ik_BYC5atnwUGSfg@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=osalvador@suse.de \
--cc=vbabka@suse.cz \
/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