From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751740AbdAWWLs convert rfc822-to-8bit (ORCPT ); Mon, 23 Jan 2017 17:11:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37432 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751319AbdAWWLq (ORCPT ); Mon, 23 Jan 2017 17:11:46 -0500 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20170123212642.GA2766@codeblueprint.co.uk> References: <20170123212642.GA2766@codeblueprint.co.uk> <20170116144954.GB27351@codeblueprint.co.uk> <20170111143304.GA29649@codeblueprint.co.uk> <148120020832.5854.5448601415491330495.stgit@warthog.procyon.org.uk> <148120024570.5854.10638278395097394138.stgit@warthog.procyon.org.uk> <7948.1484148443@warthog.procyon.org.uk> <794.1484581158@warthog.procyon.org.uk> To: Matt Fleming Cc: dhowells@redhat.com, ard.biesheuvel@linaro.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "H. Peter Anvin" , Peter Jones Subject: Re: [PATCH 5/8] efi: Get the secure boot status [ver #6] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6305.1485209502.1@warthog.procyon.org.uk> Content-Transfer-Encoding: 8BIT Date: Mon, 23 Jan 2017 22:11:43 +0000 Message-ID: <6306.1485209503@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Mon, 23 Jan 2017 22:11:46 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Matt Fleming wrote: > > (4) extract_kernel() calls sanitize_boot_params() which would otherwise clear > > the secure-boot flag. > > The ->sentinel flag should be clear (because you zero'd boot_params on > alloc), so the code inside of sanitize_boot_params() should never > trigger for the secure boot case. But it *does* trigger, otherwise I wouldn't've noticed this. David