public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
	Ard Biesheuvel
	<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: efi: Add 'capsule' update support
Date: Tue, 3 May 2016 15:50:50 +0100	[thread overview]
Message-ID: <20160503145050.GY2839@codeblueprint.co.uk> (raw)
In-Reply-To: <20160502182500.GA3461@mwanda>

On Mon, 02 May, at 09:25:00PM, Dan Carpenter wrote:
> Hello Matt Fleming,
> 
> The patch f0133f3c5b8b: "efi: Add 'capsule' update support" from Apr
> 25, 2016, leads to the following static checker warning:
> 
> 	drivers/firmware/efi/capsule.c:109 efi_capsule_supported()
> 	warn: did you mean to pass the address of 'capsule'
> 
> drivers/firmware/efi/capsule.c
>     91  int efi_capsule_supported(efi_guid_t guid, u32 flags, size_t size, int *reset)
>     92  {
>     93          efi_capsule_header_t *capsule;
>     94          efi_status_t status;
>     95          u64 max_size;
>     96          int rv = 0;
>     97  
>     98          if (flags & ~EFI_CAPSULE_SUPPORTED_FLAG_MASK)
>     99                  return -EINVAL;
>    100  
>    101          capsule = kmalloc(sizeof(*capsule), GFP_KERNEL);
>    102          if (!capsule)
>    103                  return -ENOMEM;
>    104  
>    105          capsule->headersize = capsule->imagesize = sizeof(*capsule);
>    106          memcpy(&capsule->guid, &guid, sizeof(efi_guid_t));
>    107          capsule->flags = flags;
>    108  
>    109          status = efi.query_capsule_caps(&capsule, 1, &max_size, reset);
>                                                 ^^^^^^^^
> If we modify capsule inside this function call then at the end of the
> function we aren't freeing the original pointer that we allocated.
> 
>    110          if (status != EFI_SUCCESS) {
>    111                  rv = efi_status_to_err(status);
>    112                  goto out;
>    113          }
>    114  
>    115          if (size > max_size)
>    116                  rv = -ENOSPC;
>    117  out:
>    118          kfree(capsule);
>    119          return rv;
>    120  }

We should be fine here, the firmware should not modify the argument
that we pass since we're simply querying whether or not the capsule is
supported.

Is there a cleanup that you'd suggest making to silence the static
checker warning?

  reply	other threads:[~2016-05-03 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 18:25 efi: Add 'capsule' update support Dan Carpenter
2016-05-03 14:50 ` Matt Fleming [this message]
     [not found]   ` <20160503145050.GY2839-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-05-03 15:58     ` Ard Biesheuvel
     [not found]       ` <CAKv+Gu-CBymL85xJnmC9d9nuUOuMU3kBAONWtj1-_ck4hEzxiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-04 12:12         ` Matt Fleming
     [not found]           ` <20160504121241.GI2839-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-05-04 12:28             ` Ard Biesheuvel

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=20160503145050.GY2839@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
    --cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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