From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AIpwx49J0K4o+h/zhm4pgc0Fw0jfViPalr5qF0b0aexgdabZZsD6xKfRTXSMQWHiXACKyabO2T6V ARC-Seal: i=1; a=rsa-sha256; t=1522331487; cv=none; d=google.com; s=arc-20160816; b=Y1E9l9uIXk4ZT+4vhpfvi13CWfX8xWOizwIhubwFKc3LVaUHqaSq7GOzBlqtlS6ocg YZHAGEFLuc2mk9mJi2wqmSVFBM0U5WcuWcS9wrv3PeNdRPEqPCW8A4UqJCpYHMaabVj3 Hr36rvcQ70tqJNiau74A7OXawszGeIc/VlrN8VwjjoMpXMMcX2ngFnUkpYSSnJLcYZot M5VoKC+mrnKSHr04qVkER+0T0dgRRjXRdwWGOdhebntqBxMWVzmDzJzOUeAj86AZsTIv bav+EW0uIHphfm/KHi1NBjd/U/VvU+ohhRy5z1cBBtVoST6F13HQhm1jBIRlPM/Ou005 HAUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=U/AzwZRGrb3eKJzf9KHgnqb8Bs7eAs/Gje4EZgwOY2I=; b=Er45TbLhy6XCnOj6PuzQ525pa6QaGkUUZaK2N2FmndJegsaHqIz9VWmjj3HJkPqK1h 1ESZsamF6LjCNkGjRGUwPZZdWSLig2T76rrZeQwqlkdngmB/29ceR1lOs6BaBhGPlxym kwl1+3v0pNf4Luj0L3IYCiAr8HNwM4ZR7U1pVOxsTEsOnNIFscl7bXffbMHmj2byoQ+l rnFrLkZbEXZQ+D2GlvAx7ZIv3tLh+LzAwk4Yo9FUHzAwmmZ+gy9/f99qcn42xUxWiZWT ZiXvrlOF3MVMIlgIoEmpntpO+LCP/LAZQPjjnGmzwJsK+WRgm3F0FkXzkoMwV/tlZHMQ TMGw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of dave.hansen@linux.intel.com designates 134.134.136.100 as permitted sender) smtp.mailfrom=dave.hansen@linux.intel.com Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of dave.hansen@linux.intel.com designates 134.134.136.100 as permitted sender) smtp.mailfrom=dave.hansen@linux.intel.com X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,376,1517904000"; d="scan'208";a="37877982" Subject: Re: [PATCH RFC v10 2/6] x86/entry: Add STACKLEAK erasing the kernel stack at the end of syscalls To: alex.popov@linux.com, kernel-hardening@lists.openwall.com, Kees Cook , PaX Team , Brad Spengler , Ingo Molnar , Andy Lutomirski , Tycho Andersen , Laura Abbott , Mark Rutland , Ard Biesheuvel , Borislav Petkov , Richard Sandiford , Thomas Gleixner , "H . Peter Anvin" , Peter Zijlstra , "Dmitry V . Levin" , Emese Revfy , Jonathan Corbet , Andrey Ryabinin , "Kirill A . Shutemov" , Thomas Garnier , Andrew Morton , Alexei Starovoitov , Josef Bacik , Masami Hiramatsu , Nicholas Piggin , Al Viro , "David S . Miller" , Ding Tianhong , David Woodhouse , Josh Poimboeuf , Steven Rostedt , Dominik Brodowski , Juergen Gross , Greg Kroah-Hartman , Dan Williams , Mathias Krause , Vikas Shivappa , Kyle Huey , Dmitry Safonov , Will Deacon , Arnd Bergmann , Florian Weimer , Boris Lukashev , x86@kernel.org, linux-kernel@vger.kernel.org References: <1522267032-6603-1-git-send-email-alex.popov@linux.com> <1522267032-6603-3-git-send-email-alex.popov@linux.com> <77fab6ea-0bbf-d68b-a38e-3e22d1ae6093@linux.intel.com> <16a56461-6501-7eb9-e1a4-761c9eff9386@linux.com> From: Dave Hansen Message-ID: Date: Thu, 29 Mar 2018 06:51:23 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <16a56461-6501-7eb9-e1a4-761c9eff9386@linux.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1596212693741401562?= X-GMAIL-MSGID: =?utf-8?q?1596280261144036649?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On 03/28/2018 11:58 PM, Alexander Popov wrote: >> I noticed the 64-bit version saves/restores registers while >> the 32-bit version doesn't. What's the reasoning there? > When erase_kstack() is called from the trampoline stack, it must save and > restore any modified registers, since all registers except RDI are live > (prepared for the userspace). > > When erase_kstack() is called from the thread stack, it can clobber registers > according the function call convention without any harm. Oh, and since there's no 32-bit trampoline stack, we don't need it on 32-bit? If end up reposting this set again, could you add a few comments about this around the ERASE_KSTACK macro definitions, or perhaps the call sites? You might even want to call them ERASE_KSTACK_CLOBBER (for 32-bit) and ERASE_KSTACK_NOCLOBBER (for 64-bit) to make this more clear.