From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Fleming Subject: Re: [PATCH 2/5] efibc: Fix excessive stack footprint warning Date: Wed, 11 May 2016 13:43:38 +0100 Message-ID: <20160511124338.GW2839@codeblueprint.co.uk> References: <1462570771-13324-1-git-send-email-matt@codeblueprint.co.uk> <1462570771-13324-3-git-send-email-matt@codeblueprint.co.uk> <94D0CD8314A33A4D9D801C0FE68B4029639618A2@G4W3202.americas.hpqcorp.net> <87r3dauwzt.fsf@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <87r3dauwzt.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Compostella, Jeremy" Cc: "Elliott, Robert (Persistent Memory)" , Ingo Molnar , Thomas Gleixner , "H . Peter Anvin" , Ard Biesheuvel , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Arnd Bergmann List-Id: linux-efi@vger.kernel.org On Tue, 10 May, at 10:40:22AM, Jeremy Compostella wrote: > Why not. See patch as attachment. >=20 > Thanks, >=20 > J=E9r=E9my >=20 > From 8a9b07e2d7242fa8a36157f1025202a96c3c7c9a Mon Sep 17 00:00:00 200= 1 > From: Jeremy Compostella > Date: Tue, 10 May 2016 10:34:21 +0200 > Subject: [PATCH] efibc: report the EFI variable name in the error mes= sages >=20 > Report the name of the EFI variable if the value is incorrect or if > efibc_set_variable() fails to allocate the struct efivar_entry object= =2E >=20 > Signed-off-by: Jeremy Compostella > --- > drivers/firmware/efi/efibc.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) >=20 > diff --git a/drivers/firmware/efi/efibc.c b/drivers/firmware/efi/efib= c.c > index cb4f573..93d34a1 100644 > --- a/drivers/firmware/efi/efibc.c > +++ b/drivers/firmware/efi/efibc.c > @@ -37,13 +37,14 @@ static int efibc_set_variable(const char *name, c= onst char *value) > size_t size =3D (strlen(value) + 1) * sizeof(efi_char16_t); > =20 > if (size > sizeof(entry->var.Data)) { > - pr_err("value is too large"); > + pr_err("value is too large for %s EFI variable", name); > return -EINVAL; > } It'd be a good idea to print 'size' too. > =20 > entry =3D kmalloc(sizeof(*entry), GFP_KERNEL); > if (!entry) { > - pr_err("failed to allocate efivar entry"); > + pr_err("failed to allocate efivar entry for %s EFI variable", > + name); > return -ENOMEM; > } Aren't these pr_err() calls missing newline characters?