From: Matt Domsch <Matt_Domsch@dell.com>
To: Panagiotis Issaris <panagiotis.issaris@mech.kuleuven.ac.be>
Cc: Alexey Dobriyan <adobriyan@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EFI missing failure handling
Date: Sat, 5 Mar 2005 15:18:56 -0600 [thread overview]
Message-ID: <20050305211856.GA28515@lists.us.dell.com> (raw)
In-Reply-To: <20050305201734.GA8880@mech.kuleuven.ac.be>
On Sat, Mar 05, 2005 at 09:17:34PM +0100, Panagiotis Issaris wrote:
> Hi,
>
> On Sat, Mar 05, 2005 at 07:06:29PM +0200 or thereabouts, Alexey Dobriyan wrote:
> > On Saturday 05 March 2005 17:38, Panagiotis Issaris wrote:
> >
> > > The EFI driver allocates memory and writes into it without checking the
> > > success of the allocation:
> > >
> > > 668 efi_char16_t *variable_name = kmalloc(1024, GFP_KERNEL);
> > > ...
> > > 696 memset(variable_name, 0, 1024);
> >
> > > --- linux-2.6.11-orig/drivers/firmware/efivars.c
> > > +++ linux-2.6.11-pi/drivers/firmware/efivars.c
> > > @@ -670,6 +670,9 @@ efivars_init(void)
> >
> > > + if (!variable_name)
> > > + return -ENOMEM;
> > > +
> > > if (!efi_enabled)
> > > return -ENODEV;
> >
> > I'd better move kmalloc() and checking for success down right before
> > memset(). Otherwise you leak if efi_enabled == 0.
> > Oh, and efivars_init() wants to return "error", not unconditionally 0.
> >
> > Alexey
>
> Thanks! How about the updated patch?
Looks good to me. Good catch, and thanks for the patch! Please
forward to Andrew Morton (akpm@osdl.org) directly, following the
format described here: http://linux.yyz.us/patch-format.html
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
prev parent reply other threads:[~2005-03-05 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 15:38 [PATCH] EFI missing failure handling Panagiotis Issaris
2005-03-05 17:06 ` Alexey Dobriyan
2005-03-05 20:17 ` Panagiotis Issaris
2005-03-05 21:18 ` Matt Domsch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050305211856.GA28515@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=adobriyan@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=panagiotis.issaris@mech.kuleuven.ac.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox