From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 7/7] efi_loader: Do not leak memory when unlinking a mapping
Date: Thu, 13 Oct 2016 16:35:13 +0200 [thread overview]
Message-ID: <20161013143512.35580.24011@achrid.arch.suse.de> (raw)
In-Reply-To: <286958222b7c437c9d547d0a56f3cd15@rwthex-w2-b.rwth-ad.de>
> As soon as a mapping is unlinked from the list, there are no further
> references to it, so it should be freed. If it not unlinked,
> update the start address and length.
>
> Signed-off-by: Stefan Br?ns <stefan.bruens@rwth-aachen.de>
> Reviewed-by: Alexander Graf <agraf@suse.de>
Thanks, applied to
prev parent reply other threads:[~2016-10-13 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161001213229.19522-1-stefan.bruens@rwth-aachen.de>
2016-10-01 21:32 ` [U-Boot] [PATCH v3 1/7] efi_loader: Update description of internal efi_mem_carve_out Stefan Brüns
2016-10-02 8:25 ` Alexander Graf
2016-10-13 14:35 ` [U-Boot] [U-Boot, v3, " Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 2/7] efi_loader: Fix memory map size check to avoid out-of-bounds access Stefan Brüns
2016-10-02 8:53 ` Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 3/7] efi_loader: Move efi_allocate_pool implementation to efi_memory.c Stefan Brüns
2016-10-02 8:54 ` Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 4/7] efi_loader: Track size of pool allocations to allow freeing Stefan Brüns
2016-10-02 9:04 ` Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 5/7] efi_loader: Readd freed pages to memory pool Stefan Brüns
2016-10-13 14:34 ` [U-Boot] [U-Boot, v3, " Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 6/7] efi_loader: Keep memory mapping sorted when splitting an entry Stefan Brüns
2016-10-13 14:34 ` [U-Boot] [U-Boot, v3, " Alexander Graf
2016-10-01 21:32 ` [U-Boot] [PATCH v3 7/7] efi_loader: Do not leak memory when unlinking a mapping Stefan Brüns
2016-10-13 14:35 ` Alexander Graf [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=20161013143512.35580.24011@achrid.arch.suse.de \
--to=agraf@suse.de \
--cc=u-boot@lists.denx.de \
/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