From: Vegard Nossum <vegard.nossum@oracle.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: KASAN use-after-free not showing freed stacktrace?
Date: Fri, 29 Jul 2016 23:55:54 +0200 [thread overview]
Message-ID: <579BD0EA.2070005@oracle.com> (raw)
In-Reply-To: <CACT4Y+awRa0Szpq1fz_eSge=LHBPDfiewEJJQR6eyqgKUE_Kag@mail.gmail.com>
On 07/29/2016 11:27 PM, Dmitry Vyukov wrote:
> On Fri, Jul 29, 2016 at 10:17 PM, Vegard Nossum
> <vegard.nossum@oracle.com> wrote:
>> Hi again,
>>
>> I am seeing some KASAN use-after-free bugs now but there is no
>> stacktrace for where they were freed anymore:
[...]
>> That seems like a regression, maybe related to memory quarantine
>> for SLUB? Or is there something else going on?
> Do you use SLAB or SLUB? Is CONFIG_STACKDEPOT enabled? Kernel revision?
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLAB_FREELIST_RANDOM=y
CONFIG_SLUB_CPU_PARTIAL=y
CONFIG_SLABINFO=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_FAILSLAB=y
CONFIG_STACKDEPOT=y
git version c624c86615fb8aa61fa76ed8c935446d06c80e77
Vegard
prev parent reply other threads:[~2016-07-29 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 20:17 KASAN use-after-free not showing freed stacktrace? Vegard Nossum
2016-07-29 21:27 ` Dmitry Vyukov
2016-07-29 21:55 ` Vegard Nossum [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=579BD0EA.2070005@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox