From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1426713AbcBRRyy (ORCPT ); Thu, 18 Feb 2016 12:54:54 -0500 Received: from foss.arm.com ([217.140.101.70]:41416 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1426666AbcBRRyw (ORCPT ); Thu, 18 Feb 2016 12:54:52 -0500 Date: Thu, 18 Feb 2016 17:54:47 +0000 From: Catalin Marinas To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Lorenzo Pieralisi , Ard Biesheuvel , Will Deacon , mingo@kernel.org, Andrey Ryabinin , akpm@linux-foundation.org, hpa@linux.intel.com, tglx@linutronix.de Subject: Re: [PATCH] arm64: kasan: clear stale stack poison Message-ID: <20160218175447.GD2538@e104818-lin.cambridge.arm.com> References: <1455816458-19485-1-git-send-email-mark.rutland@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1455816458-19485-1-git-send-email-mark.rutland@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 18, 2016 at 05:27:38PM +0000, Mark Rutland wrote: > @@ -145,6 +146,7 @@ ENTRY(cpu_resume_mmu) > ENDPROC(cpu_resume_mmu) > .popsection > cpu_resume_after_mmu: > + kasan_unpoison_stack 96 I don't think the 96 here is needed since we populate the stack in assembly (__cpu_suspend_enter) and unwind it again still in assembly (cpu_resume_after_mmu), so no KASAN shadow writes/reads. Otherwise the patch looks fine. -- Catalin