From: Qian Cai <cai@lca.pw>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: CONFIG_KASAN_SW_TAGS=y NULL pointer dereference at freelist_dereference()
Date: Thu, 7 Feb 2019 19:30:10 -0500 [thread overview]
Message-ID: <d8cdc634-0f7d-446e-805a-c5d54e84323a@lca.pw> (raw)
In-Reply-To: <CAAeHK+zxxk8K3WjGYutmPZr_mX=u7KUcCUYXHi+OgRYMfcvLTg@mail.gmail.com>
On 2/7/19 10:34 AM, Andrey Konovalov wrote:
> Reproduced, looks like a conflict with CONFIG_SLAB_FREELIST_HARDENED.
> Could you try the attached patch?
>
You nailed it!
WARNING: multiple messages have this Message-ID (diff)
From: Qian Cai <cai@lca.pw>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: kasan-dev <kasan-dev@googlegroups.com>,
Linux-MM <linux-mm@kvack.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: CONFIG_KASAN_SW_TAGS=y NULL pointer dereference at freelist_dereference()
Date: Thu, 7 Feb 2019 19:30:10 -0500 [thread overview]
Message-ID: <d8cdc634-0f7d-446e-805a-c5d54e84323a@lca.pw> (raw)
In-Reply-To: <CAAeHK+zxxk8K3WjGYutmPZr_mX=u7KUcCUYXHi+OgRYMfcvLTg@mail.gmail.com>
On 2/7/19 10:34 AM, Andrey Konovalov wrote:
> Reproduced, looks like a conflict with CONFIG_SLAB_FREELIST_HARDENED.
> Could you try the attached patch?
>
You nailed it!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-08 0:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 4:04 CONFIG_KASAN_SW_TAGS=y NULL pointer dereference at freelist_dereference() Qian Cai
2019-02-07 4:04 ` Qian Cai
2019-02-07 12:58 ` Andrey Konovalov
2019-02-07 12:58 ` Andrey Konovalov
2019-02-07 13:27 ` Qian Cai
2019-02-07 13:27 ` Qian Cai
2019-02-07 15:34 ` Andrey Konovalov
2019-02-07 15:34 ` Andrey Konovalov
2019-02-08 0:30 ` Qian Cai [this message]
2019-02-08 0:30 ` Qian Cai
2019-02-08 4:16 ` CONFIG_KASAN_SW_TAGS=y not play well with kmemleak Qian Cai
2019-02-08 17:15 ` Andrey Konovalov
2019-02-08 17:15 ` Andrey Konovalov
2019-02-09 2:17 ` Qian Cai
2019-02-09 2:17 ` Qian Cai
2019-02-11 12:15 ` Catalin Marinas
2019-02-11 12:15 ` Catalin Marinas
2019-02-11 18:52 ` Andrey Konovalov
2019-02-11 18:52 ` Andrey Konovalov
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=d8cdc634-0f7d-446e-805a-c5d54e84323a@lca.pw \
--to=cai@lca.pw \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.