Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp9453269ybi; Wed, 24 Jul 2019 04:24:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqyzg5FIe7lmFSdqHZVWUl9wE1Acc6Bx3k8yTe+MWezpKuQqLbYg+kiDOf5Ov4FhvKHAKhpU X-Received: by 2002:aa7:8804:: with SMTP id c4mr10754938pfo.65.1563967484040; Wed, 24 Jul 2019 04:24:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563967484; cv=none; d=google.com; s=arc-20160816; b=KW6FFAO+yEnurdopbgMMpmQcJv3JrdqWOgrX8IYNvMS7zP7PLUL0Oiq0Br2AdrsXL2 5AxASBUp/ibv5OK2s/pOo5qaa8P5MEwv94IvBaVefilsNj1ymopEItGEpwPwVJq57XWP 1Mz/9i8DXJ/nC2gCoVtHPdnqAh5Ahn/gTEHkUDtYzmySQWLYY/mlBTv4z3wBAD9YQBnN xTmiPLcT0ZmaGa7TAr24HQdi1AhcXywCxIpArYlvygWdTTFgcrSpl4vk8Nx5JgIWDg/U Bc9HYliCKh2Iy58G6nlIIM8f2b8zRj6PiUJFU05udnQfwST7+HfXJJTG3x0iPHbd7RJe I+EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=pA/QbGG5emYrgtlKOSirjwbDA4VTCh+pBSNZ0yF96nQ=; b=KvCi3H+X1/ADfs7O+qKL/PxFu8brAsM8ykheI9LoJn65QzVE3rshnEzQTtf0ecXAF0 y117X3et4tCjfZlOBsVfi1Qmu6UKHiiqVgxwF9gnHRWeK3hJ9mBooG6sYp/OL22BioZk xXPb57fECVWav5gOTiRVd0zbzJ2l95GPlV8SaUbJ1hPvKVexQysspykGorkCECuybzzs e0lL98G4f78oJPmdi/qE0bLQoaLCXBsIhsrtHR4eeG4CINiz56O/s2t6EI422gzdT08J ju1E7WaIPm4yn9IwV3oGElTS1loH8naocnBu9/ngWyZVUO1k5TAkx8h4megTS413pBen XW9w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v184si13083255pgd.278.2019.07.24.04.24.29; Wed, 24 Jul 2019 04:24:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727404AbfGXLXY (ORCPT + 99 others); Wed, 24 Jul 2019 07:23:24 -0400 Received: from foss.arm.com ([217.140.110.172]:39382 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726087AbfGXLXX (ORCPT ); Wed, 24 Jul 2019 07:23:23 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 286A0337; Wed, 24 Jul 2019 04:23:23 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 72B4C3F71A; Wed, 24 Jul 2019 04:23:21 -0700 (PDT) Date: Wed, 24 Jul 2019 12:23:19 +0100 From: Mark Rutland To: Marco Elver Cc: LKML , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Andrey Konovalov , Peter Zijlstra , the arch/x86 maintainers , kasan-dev Subject: Re: [PATCH 2/2] lib/test_kasan: Add stack overflow test Message-ID: <20190724112318.GC2624@lakrids.cambridge.arm.com> References: <20190719132818.40258-1-elver@google.com> <20190719132818.40258-2-elver@google.com> <20190723162403.GA56959@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 23, 2019 at 06:49:03PM +0200, Marco Elver wrote: > On Tue, 23 Jul 2019 at 18:24, Mark Rutland wrote: > > > > On Fri, Jul 19, 2019 at 03:28:18PM +0200, Marco Elver wrote: > > > Adds a simple stack overflow test, to check the error being reported on > > > an overflow. Without CONFIG_STACK_GUARD_PAGE, the result is typically > > > some seemingly unrelated KASAN error message due to accessing random > > > other memory. > > > > Can't we use the LKDTM_EXHAUST_STACK case to check this? > > > > I was also under the impression that the other KASAN self-tests weren't > > fatal, and IIUC this will kill the kernel. > > > > Given that, and given this is testing non-KASAN functionality, I'm not > > sure it makes sense to bundle this with the KASAN tests. > > Thanks for pointing out LKDTM_EXHAUST_STACK. > > This patch can be dropped! Cool; it's always nice to find the work has already been done! :) Thanks, Mark.