All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org"
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org"
	<bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
	"leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
	<roy.franz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] efi: stub: call get_memory_map() to obtain map and desc sizes
Date: Thu, 8 Jan 2015 19:04:26 +0000	[thread overview]
Message-ID: <20150108190426.GC31280@leverpostej> (raw)
In-Reply-To: <1420739507-1708-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>

Hi Ard,

On Thu, Jan 08, 2015 at 05:51:47PM +0000, Ard Biesheuvel wrote:
> This fixes two minor issues in the implementation of get_memory_map():
> - Currently, it assumes that sizeof(efi_memory_desc_t) == desc_size,
>   which is usually true, but not mandated by the spec. (This was added
>   intentionally to allow future additions to the definition of
>   efi_memory_desc_t). The way the loop is implemented currently, the
>   added slack space may be insufficient if desc_size is larger, which in
>   some corner cases could result in the loop never terminating.
> - It allocates 32 efi_memory_desc_t entries first (again, using the size
>   of the struct instead of desc_size), and frees and reallocates if it
>   turns out to be insufficient. Few implementations of UEFI have such small
>   memory maps, which results in a unnecessary allocate/free pair on each
>   invocation.
> 
> Fix this by calling the get_memory_map() boot service first with a '0'
> input value for map size to retrieve the map size and desc size from the
> firmware and only then perform the allocation, using desc_size rather
> than sizeof(efi_memory_desc_t).

Is the desc_size guaranteed to be set up correctly if the size is too
small?

As far as I can see, for that case the spec only mandates that
MemoryMapSize is updated nd EFI_BUFFER_TOO_SMALL is returned.

It's not clear to me whether DescriptorSize or DescriptorVersion are
initialised in cases other than success.

Thanks,
Mark.

> 
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
>  drivers/firmware/efi/libstub/efi-stub-helper.c | 16 ++++++++++------
>  1 file changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/firmware/efi/libstub/efi-stub-helper.c b/drivers/firmware/efi/libstub/efi-stub-helper.c
> index e766df60fbfb..caf91eab0bfc 100644
> --- a/drivers/firmware/efi/libstub/efi-stub-helper.c
> +++ b/drivers/firmware/efi/libstub/efi-stub-helper.c
> @@ -75,25 +75,29 @@ efi_status_t efi_get_memory_map(efi_system_table_t *sys_table_arg,
>  	unsigned long key;
>  	u32 desc_version;
>  
> -	*map_size = sizeof(*m) * 32;
> -again:
> +	*map_size = 0;
> +	*desc_size = 0;
> +	key = 0;
> +	status = efi_call_early(get_memory_map, map_size, NULL,
> +				&key, desc_size, &desc_version);
> +	if (status != EFI_BUFFER_TOO_SMALL)
> +		return EFI_LOAD_ERROR;
> +
>  	/*
>  	 * Add an additional efi_memory_desc_t because we're doing an
>  	 * allocation which may be in a new descriptor region.
>  	 */
> -	*map_size += sizeof(*m);
> +	*map_size += *desc_size;
>  	status = efi_call_early(allocate_pool, EFI_LOADER_DATA,
>  				*map_size, (void **)&m);
>  	if (status != EFI_SUCCESS)
>  		goto fail;
>  
> -	*desc_size = 0;
> -	key = 0;
>  	status = efi_call_early(get_memory_map, map_size, m,
>  				&key, desc_size, &desc_version);
>  	if (status == EFI_BUFFER_TOO_SMALL) {
>  		efi_call_early(free_pool, m);
> -		goto again;
> +		return EFI_LOAD_ERROR;
>  	}
>  
>  	if (status != EFI_SUCCESS)
> -- 
> 1.8.3.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-efi" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  parent reply	other threads:[~2015-01-08 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 17:51 [PATCH] efi: stub: call get_memory_map() to obtain map and desc sizes Ard Biesheuvel
     [not found] ` <1420739507-1708-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-08 19:04   ` Mark Rutland [this message]
2015-01-08 19:09     ` Ard Biesheuvel
     [not found]       ` <CAKv+Gu9tVjfU5S=3oLTznUFnv0WAbGcKueNjKtDtYqGQ+cxtxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-09 10:19         ` Mark Rutland
2015-01-09 10:55           ` Leif Lindholm
     [not found]             ` <20150109105529.GP3827-t77nlHhSwNqAroYi2ySoxKxOck334EZe@public.gmane.org>
2015-01-09 11:16               ` Mark Rutland
2015-01-12 11:09               ` Matt Fleming

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=20150108190426.GC31280@leverpostej \
    --to=mark.rutland-5wv7dgnigg8@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
    --cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=roy.franz-QSEj5FYQhm4dnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.