From: Will Deacon <will.deacon@arm.com>
To: Qian Cai <cai@lca.pw>
Cc: Andrey Konovalov <andreyknvl@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
kasan-dev <kasan-dev@googlegroups.com>,
aryabinin@virtuozzo.com
Subject: Re: livelock with KASAN_SW_TAGS
Date: Thu, 14 Feb 2019 18:01:25 +0000 [thread overview]
Message-ID: <20190214180125.GH2475@fuggles.cambridge.arm.com> (raw)
In-Reply-To: <50ef4f07-af09-5498-2bca-26ced76d9736@lca.pw>
On Thu, Feb 14, 2019 at 11:50:59AM -0500, Qian Cai wrote:
> On 2/14/19 11:35 AM, Will Deacon wrote:
> > On Wed, Feb 13, 2019 at 10:32:11PM -0500, Qian Cai wrote:
> >> Running LTP msgstress03 [1] triggers endless soft lockups below after a few
> >> minutes on a ThunderX2 server. It works fine with KASAN_GENERIC and finish the
> >> test in roughly 11 minutes.
> >
> > I've not been able to reproduce this failure under KVM, however the test
> > only takes around 18s to complete on the host and the guest, so it feels
> > like something is amiss here. Please could you share more information about
> > how you're triggering this problem? For example:
> >
> > - Kernel version and .config
>
> Latest mainline at 1f947a7a01 ("Merge branch 'akpm' (patches from Andrew)") plus
> a few KASAN_SW_TAGS patches in order to boot.
>
> https://marc.info/?l=linux-mm&m=155006632110129&w=2 (all 5)
> https://marc.info/?l=linux-mm&m=154968731424637&w=2
> https://marc.info/?l=linux-mm&m=155010395725051&w=2
>
> https://git.sr.ht/~cai/linux-debug/tree/master/config
I struggled to get this config to boot under KVM :(
> > - Clang version
>
> clang-7.0.1
It would be helpful to know if the issue persists with the latest nightly
build of clang.
Anyway, please could you annotate the goto loop in free_debug_processing()
so that the object and tail pointer are printed each time around? It would
be useful to know if we're failing to exit that.
Thanks,
Will
_______________________________________________
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-14 18:01 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 [this message]
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
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=20190214180125.GH2475@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.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.