From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from s3.sipsolutions.net ([2a01:4f8:191:4433::2] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j2W0o-0002Dx-Aa for linux-um@lists.infradead.org; Fri, 14 Feb 2020 08:07:48 +0000 Message-ID: Subject: Re: [RFC PATCH v2] UML: add support for KASAN under x86_64 From: Johannes Berg Date: Fri, 14 Feb 2020 09:07:27 +0100 In-Reply-To: (sfid-20200214_015457_457274_397896E3) References: <20200210225806.249297-1-trishalfonso@google.com> <13b0ea0caff576e7944e4f9b91560bf46ac9caf0.camel@sipsolutions.net> (sfid-20200214_015457_457274_397896E3) MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-um" Errors-To: linux-um-bounces+geert=linux-m68k.org@lists.infradead.org To: Patricia Alfonso Cc: Richard Weinberger , Jeff Dike , Brendan Higgins , LKML , kasan-dev , linux-um@lists.infradead.org, David Gow , Andrey Ryabinin , Dmitry Vyukov , anton.ivanov@cambridgegreys.com 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 _______________________________________________ linux-um mailing list linux-um@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-um