Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753088AbbDFSj5 (ORCPT ); Mon, 6 Apr 2015 14:39:57 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:32807 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752935AbbDFSjx (ORCPT ); Mon, 6 Apr 2015 14:39:53 -0400 Date: Mon, 6 Apr 2015 19:39:49 +0100 From: Matt Fleming To: Ross Lagerwall Cc: linux-efi@vger.kernel.org, Matthew Garrett , Jeremy Kerr , Matt Fleming , linux-kernel@vger.kernel.org Subject: Re: [PATCH RESEND] efivarfs: Ensure VariableName is NUL-terminated Message-ID: <20150406183949.GA7511@codeblueprint.co.uk> References: <1427960340-5339-1-git-send-email-ross.lagerwall@citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1427960340-5339-1-git-send-email-ross.lagerwall@citrix.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1131 Lines: 31 On Thu, 02 Apr, at 08:39:00AM, Ross Lagerwall wrote: > Some buggy firmware implementations update VariableNameSize on success > such that it does not include the final NUL character which results in > garbage in the efivarfs name entries. Use kzalloc on the efivar_entry > (as is done in efivars.c) to ensure that the name is always > NUL-terminated. > > The buggy firmware is: > BIOS Information > Vendor: Intel Corp. > Version: S1200RP.86B.02.02.0005.102320140911 > Release Date: 10/23/2014 > BIOS Revision: 4.6 > System Information > Manufacturer: Intel Corporation > Product Name: S1200RP_SE > > Signed-off-by: Ross Lagerwall > --- > fs/efivarfs/super.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Thanks, applied with Matthew's ACK! -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/