[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d8151ac6b1e590d6c49d8c890604a08685cd2303.camel@sipsolutions.net>
Date: Fri, 14 Feb 2020 09:07:27 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Patricia Alfonso <trishalfonso@...gle.com>
Cc: Jeff Dike <jdike@...toit.com>, Richard Weinberger <richard@....at>,
anton.ivanov@...bridgegreys.com,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
David Gow <davidgow@...gle.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
kasan-dev <kasan-dev@...glegroups.com>,
LKML <linux-kernel@...r.kernel.org>, linux-um@...ts.infradead.org
Subject: Re: [RFC PATCH v2] UML: add support for KASAN under x86_64
On Thu, 2020-02-13 at 16:54 -0800, Patricia Alfonso wrote:
> Okay, so I'll rebase onto (1) and just add the lines I need from the
> [DEMO]. Are you sure you don't want to be named as a co-developed-by
> at least?
Yeah ... it's like 3 lines of code? Don't worry about it :)
> Yeah, failing loudly does seem to be the best option here.
I just ran into that with userspace ASAN yesterday for some reason, so
yeah.
Perhaps good to tell people what to do - I couldn't actually solve the
issue I had in userspace yesterday. Here, could tell people to check the
address where it's mapped, or so?
johannes
Powered by blists - more mailing lists