Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3194495imm; Tue, 17 Jul 2018 00:08:26 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfV6Ze4uRQBrIhR/YbfBKHYU9pkBdKqSmdn3yVA3BBDBOXIkQutI2aYDTf8Oz/tkpdaZy8V X-Received: by 2002:a17:902:5a1:: with SMTP id f30-v6mr449748plf.167.1531811306232; Tue, 17 Jul 2018 00:08:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531811306; cv=none; d=google.com; s=arc-20160816; b=Qd6tvvQsOHxgh4wI2/LOCnJ35UMcawBneqi5ok7mzNMgeHRx7tfnCTn5bmo6CaQ1ju CStSRV4AYcpxE4VCcbty2uIjkNCn7pMdbSi8RVY0FtH0/Xe30jeW8X650Sm8QUG2m9vE IsTSwWGvw4nUxjuBSW8MwYdKF/Bi3OOyvbhNR+JcZ90KXgHVTYd98fXDFUfVgydXQdW3 ayOmiDdolhgJ5MuDCz+0jGgZ8fIz0DIdiltfpolsOL2avdUxntGlaImypAlNPECixrD8 mgV855vFeYMa3BXeJCYWjOB7//8LgMsttCfuRRLaisk8bB00pZHYzbFk/uYrNzSrCX82 6Ixw== 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:arc-authentication-results; bh=qIc9l6QCRTIGEEdbk3TQ1dLkBvhugfUon4o5unJB0mQ=; b=YdBADF4jPSOG6Oz0Bco5589NFPmPtIKcgAGR/ayaWjNBrIqWWq/ak8XwIuM1KaKCkX 0Hz2FIiIkPVqPDle8l6OKkhuO2nvq16i81uokZm4eSJ25Gq/N2ZMekeQwVI4bQ07AFYE ulBACpeaULjEwOd25oWEAvCOvnXUI8v6eQaqiaeTSHbAN/0koiHFgLbMP7ivVdPqNUNa pxzhDlaqUj6JGuOKpJhW2uYMEE7wDMpcn7Xeqrm9C4JoFL9Rr4tSZFGzHnef3RxLXMDn sNwqOREY68dSS60wyNNQoPpRPKkbrJ18CMHOHIFmvdnYXsyJhV4YmK/0xbwAj9vmUb8L Lb2A== 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 16-v6si220185pgr.325.2018.07.17.00.08.10; Tue, 17 Jul 2018 00:08:26 -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 S1728330AbeGQHih (ORCPT + 99 others); Tue, 17 Jul 2018 03:38:37 -0400 Received: from mx2.suse.de ([195.135.220.15]:50632 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727625AbeGQHih (ORCPT ); Tue, 17 Jul 2018 03:38:37 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 0EB83AE62; Tue, 17 Jul 2018 07:07:28 +0000 (UTC) Date: Tue, 17 Jul 2018 09:07:25 +0200 From: Joerg Roedel To: Andy Lutomirski Cc: Joerg Roedel , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , X86 ML , LKML , Linux-MM , Linus Torvalds , Andy Lutomirski , Dave Hansen , Josh Poimboeuf , Juergen Gross , Peter Zijlstra , Borislav Petkov , Jiri Kosina , Boris Ostrovsky , Brian Gerst , David Laight , Denys Vlasenko , Eduardo Valentin , Greg KH , Will Deacon , "Liguori, Anthony" , Daniel Gruss , Hugh Dickins , Kees Cook , Andrea Arcangeli , Waiman Long , Pavel Machek , "David H . Gutteridge" Subject: Re: [PATCH 07/39] x86/entry/32: Enter the kernel via trampoline stack Message-ID: <20180717070725.paxlewuu4z4qd3cu@suse.de> References: <1531308586-29340-1-git-send-email-joro@8bytes.org> <1531308586-29340-8-git-send-email-joro@8bytes.org> <20180713105620.z6bjhqzfez2hll6r@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 13, 2018 at 10:21:39AM -0700, Andy Lutomirski wrote: > On Fri, Jul 13, 2018 at 3:56 AM, Joerg Roedel wrote: > > Right, I implement a more restrictive check. > > But the check needs to be correct or we'll mess up, right? I think > the code will be much more robust and easier to review if you check > "on the entry stack" instead of ">= the entry stack". (Or <= -- I can > never remember how this works in AT&T syntax.) Yeah, I re-used the check implemented on the NMI entry path, it checks exactly for the entry-stack range. Regards, Joerg