From: "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lee Chun-Yi <jlee@suse.com>, Dave Young <dyoung@redhat.com>,
Borislav Petkov <bp@alien8.de>, Laszlo Ersek <lersek@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
Bhupesh Sharma <bhsharma@redhat.com>,
Nicolai Stange <nicstange@gmail.com>,
Naresh Bhat <naresh.bhat@linaro.org>,
"Neri, Ricardo" <ricardo.neri@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
"Williams, Dan J" <dan.j.williams@intel.com>
Subject: RE: [PATCH 1/6] efi: Introduce efi_memmap_free() to free memory allocated by efi_memmap_alloc()
Date: Thu, 5 Jul 2018 18:30:33 +0000 [thread overview]
Message-ID: <FFF73D592F13FD46B8700F0A279B802F4659B195@ORSMSX111.amr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu8FjCojLTckLVcOq1z4e=pp4U8GQWVHpvHTewRgef6HDg@mail.gmail.com>
> > Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
> > Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Cc: Lee Chun-Yi <jlee@suse.com>
> > Cc: Dave Young <dyoung@redhat.com>
> > Cc: Borislav Petkov <bp@alien8.de>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Jan Kiszka <jan.kiszka@siemens.com>
> > Cc: Dave Hansen <dave.hansen@intel.com>
> > Cc: Bhupesh Sharma <bhsharma@redhat.com>
> > Cc: Nicolai Stange <nicstange@gmail.com>
> > Cc: Naresh Bhat <naresh.bhat@linaro.org>
> > Cc: Ricardo Neri <ricardo.neri@intel.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Taku Izumi <izumi.taku@jp.fujitsu.com>
> > Cc: Ravi Shankar <ravi.v.shankar@intel.com>
> > Cc: Matt Fleming <matt@codeblueprint.co.uk>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Do you really think you should cc all these people?
>
Sorry! I get that..
> > ---
> > drivers/firmware/efi/memmap.c | 28 ++++++++++++++++++++++++++++
> > include/linux/efi.h | 8 ++++++++
> > 2 files changed, 36 insertions(+)
> >
[snip]
> I am now thinking we should perhaps hide the allocation type from the callers
> rather than passing around implementation details of the allocator, and have
> explicit alloc/free operations.
>
> Could we instead have a single 'efi_realloc_memmap()' function that takes care
> of all of this?
Sure! I will give it a try.
Regards,
Sai
next prev parent reply other threads:[~2018-07-05 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 1:50 [PATCH 0/6] Fix memory leaks in efi subsystem Sai Praneeth Prakhya
2018-07-03 1:50 ` [PATCH 1/6] efi: Introduce efi_memmap_free() to free memory allocated by efi_memmap_alloc() Sai Praneeth Prakhya
2018-07-05 9:29 ` Ard Biesheuvel
2018-07-05 18:30 ` Prakhya, Sai Praneeth [this message]
2018-07-03 1:50 ` [PATCH 2/6] efi: Let the user of efi_memmap_alloc() know the type of allocation performed Sai Praneeth Prakhya
2018-07-03 1:50 ` [PATCH 3/6] efi: Use efi.memmap.alloc_type instead of efi.memmap.late Sai Praneeth Prakhya
2018-07-03 1:50 ` [PATCH 4/6] x86/efi: Free existing memory map before installing new memory map Sai Praneeth Prakhya
2018-07-03 1:50 ` [PATCH 5/6] x86/efi: Free allocated memory if remap fails Sai Praneeth Prakhya
2018-07-03 1:50 ` [PATCH 6/6] efi: Fix unaligned fake memmap entries corrupting efi memory map Sai Praneeth Prakhya
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=FFF73D592F13FD46B8700F0A279B802F4659B195@ORSMSX111.amr.corp.intel.com \
--to=sai.praneeth.prakhya@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dyoung@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jan.kiszka@siemens.com \
--cc=jlee@suse.com \
--cc=lersek@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=naresh.bhat@linaro.org \
--cc=nicstange@gmail.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
/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
all inboxes | Powered by JetHome®