All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Trammell Hudson <hudson@trmm.net>
Cc: xen-devel@lists.xenproject.org, roger.pau@citrix.com,
	andrew.cooper3@citrix.com, wl@xen.org
Subject: Re: [PATCH v8 1/5] efi/boot.c: add file.need_to_free
Date: Fri, 2 Oct 2020 10:15:08 +0200	[thread overview]
Message-ID: <76a21a35-0469-6d44-564a-c0fed9bf9bfd@suse.com> (raw)
In-Reply-To: <20200930120011.1622924-2-hudson@trmm.net>

On 30.09.2020 14:00, Trammell Hudson wrote:
> The config file, kernel, initrd, etc should only be freed if they
> are allocated with the UEFI allocator.  On x86 the ucode, and on
> ARM the dtb, are also marked as need_to_free when allocated or
> expanded.
> 
> This also fixes a memory leak in ARM fdt_increase_size() if there
> is an error in building the new device tree.
> 
> Signed-off-by: Trammell Hudson <hudson@trmm.net>

Reviewed-by: Jan Beulich <jbeulich@suse.com>



  reply	other threads:[~2020-10-02  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 12:00 [PATCH v8 0/5] efi: Unified Xen hypervisor/kernel/initrd images Trammell Hudson
2020-09-30 12:00 ` [PATCH v8 1/5] efi/boot.c: add file.need_to_free Trammell Hudson
2020-10-02  8:15   ` Jan Beulich [this message]
2020-09-30 12:00 ` [PATCH v8 2/5] efi/boot.c: add handle_file_info() Trammell Hudson
2020-09-30 12:00 ` [PATCH v8 3/5] efi/boot.c: wrap PrintStr/PrintErr to allow const CHAR16* arguments Trammell Hudson
2020-09-30 12:15   ` Jan Beulich
2020-09-30 12:33     ` Trammell Hudson
2020-09-30 12:00 ` [PATCH v8 4/5] efi: Enable booting unified hypervisor/kernel/initrd images Trammell Hudson
2020-10-02  8:27   ` Jan Beulich
2020-10-02 10:52     ` Trammell Hudson
2020-09-30 12:00 ` [PATCH v8 5/5] efi: Do not use command line if unified config is included Trammell Hudson

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=76a21a35-0469-6d44-564a-c0fed9bf9bfd@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=hudson@trmm.net \
    --cc=roger.pau@citrix.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.