From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Fleming Subject: Re: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels Date: Mon, 30 May 2016 22:12:12 +0100 Message-ID: <20160530211212.GG2984@codeblueprint.co.uk> References: <1464189116-30898-1-git-send-email-mark.rutland@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1464189116-30898-1-git-send-email-mark.rutland-5wv7dgnIgG8@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Mark Rutland Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Ard Biesheuvel , Catalin Marinas , Jeremy Linton , Leif Lindholm , Will Deacon , linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-efi@vger.kernel.org On Wed, 25 May, at 04:11:56PM, Mark Rutland wrote: > > No further restriction on alignment is provided in the UEFI > specification, neither generically nor in a rule specific to AArch64. This surprises me. I could have sworn the intention was to add this restriction to the spec when the strict permissions were being discussed in the UEFI working groups. Am I reinventing history? As an aside, Mark, Jeremy, which machines did you see this warning triggered on? Preproduction/development boards or also in the wild? From mboxrd@z Thu Jan 1 00:00:00 1970 From: matt@codeblueprint.co.uk (Matt Fleming) Date: Mon, 30 May 2016 22:12:12 +0100 Subject: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels In-Reply-To: <1464189116-30898-1-git-send-email-mark.rutland@arm.com> References: <1464189116-30898-1-git-send-email-mark.rutland@arm.com> Message-ID: <20160530211212.GG2984@codeblueprint.co.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, 25 May, at 04:11:56PM, Mark Rutland wrote: > > No further restriction on alignment is provided in the UEFI > specification, neither generically nor in a rule specific to AArch64. This surprises me. I could have sworn the intention was to add this restriction to the spec when the strict permissions were being discussed in the UEFI working groups. Am I reinventing history? As an aside, Mark, Jeremy, which machines did you see this warning triggered on? Preproduction/development boards or also in the wild?