From: Qian Cai <cai@lca.pw>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: soft lockups with SLAB_CONSISTENCY_CHECKS + KASAN_SW_TAGS (was: livelock with KASAN_SW_TAGS)
Date: Tue, 19 Feb 2019 14:08:00 -0500 [thread overview]
Message-ID: <1550603280.6911.43.camel@lca.pw> (raw)
In-Reply-To: <CAAeHK+yUQ0kZUspiFazjkFu7CRdaL_DZijUXD1po45gnGZkV3w@mail.gmail.com>
On Tue, 2019-02-19 at 19:56 +0100, Andrey Konovalov wrote:
> Ah, so it doesn't lock, it's just very slow? memchr_inv() is the only
> caller of check_bytes8(), so we could remove instrumentation from the
> latter, and add one KASAN range check into the former. But I'd say
> this is the expected behavior, KASAN slows down stuff and I don't
> think it makes much sense to enable it together with other memory
> debugging options.
>
Yes, just very slow.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-19 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 3:32 livelock with KASAN_SW_TAGS Qian Cai
2019-02-14 16:35 ` Will Deacon
2019-02-14 16:50 ` Qian Cai
2019-02-14 18:01 ` Will Deacon
2019-02-15 4:04 ` Qian Cai
2019-02-15 14:23 ` Will Deacon
2019-02-15 14:26 ` Will Deacon
2019-02-19 17:56 ` Andrey Konovalov
[not found] ` <1550601754.6911.41.camel@lca.pw>
2019-02-19 18:56 ` soft lockups with SLAB_CONSISTENCY_CHECKS + KASAN_SW_TAGS (was: livelock with KASAN_SW_TAGS) Andrey Konovalov
2019-02-19 19:08 ` Qian Cai [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=1550603280.6911.43.camel@lca.pw \
--to=cai@lca.pw \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will.deacon@arm.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 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.