From: Darren Hart <dvhart@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
"Andy Shevchenko" <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
"Mihai Donțu" <mihai.dontu@gmail.com>,
Mario.Limonciello@dell.com
Subject: Re: [PATCH] platform/x86: wmi: Do not mix pages and kmalloc
Date: Wed, 20 Jun 2018 16:37:36 -0700 [thread overview]
Message-ID: <20180620233736.GA3250@fury> (raw)
In-Reply-To: <20180620213141.GA8957@beast>
On Wed, Jun 20, 2018 at 02:31:41PM -0700, Kees Cook wrote:
> The probe handler_data was being allocated with __get_free_pages()
> for no reason I could find. The error path was using kfree(). Since
v4 of Mario's series used kmalloc:
https://patchwork.kernel.org/patch/9985827/
This was changed in v10 to use __get_free_pages:
https://patchwork.kernel.org/patch/10018023/
But... I'm not finding the discussion that led to this change.... Mario,
do you recall? Something about contiguous memory? We had a similar
discussion on an earlier series:
https://patchwork.kernel.org/patch/9975277/
> other things are happily using kmalloc() in the probe path, switch to
> kmalloc() entirely. This fixes the error path mismatch and will avoid
> issues with CONFIG_HARDENED_USERCOPY_PAGESPAN=y.
>
> Reported-by: Mihai Donțu <mihai.dontu@gmail.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> drivers/platform/x86/wmi.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
> index 8e3d0146ff8c..04791ea5d97b 100644
> --- a/drivers/platform/x86/wmi.c
> +++ b/drivers/platform/x86/wmi.c
> @@ -895,7 +895,6 @@ static int wmi_dev_probe(struct device *dev)
> struct wmi_driver *wdriver =
> container_of(dev->driver, struct wmi_driver, driver);
> int ret = 0;
> - int count;
> char *buf;
>
> if (ACPI_FAILURE(wmi_method_enable(wblock, 1)))
> @@ -917,9 +916,8 @@ static int wmi_dev_probe(struct device *dev)
> goto probe_failure;
> }
>
> - count = get_order(wblock->req_buf_size);
> - wblock->handler_data = (void *)__get_free_pages(GFP_KERNEL,
> - count);
> + wblock->handler_data = kmalloc(wblock->req_buf_size,
> + GFP_KERNEL);
> if (!wblock->handler_data) {
> ret = -ENOMEM;
> goto probe_failure;
> @@ -964,8 +962,7 @@ static int wmi_dev_remove(struct device *dev)
> if (wdriver->filter_callback) {
> misc_deregister(&wblock->char_dev);
> kfree(wblock->char_dev.name);
> - free_pages((unsigned long)wblock->handler_data,
> - get_order(wblock->req_buf_size));
> + kfree(wblock->handler_data);
> }
>
> if (wdriver->remove)
> --
> 2.17.1
>
>
> --
> Kees Cook
> Pixel Security
>
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-06-20 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 21:31 [PATCH] platform/x86: wmi: Do not mix pages and kmalloc Kees Cook
2018-06-20 23:37 ` Darren Hart [this message]
2018-06-20 23:43 ` Kees Cook
2018-06-21 0:17 ` Darren Hart
2018-06-21 1:24 ` Mario.Limonciello
2018-06-22 23:27 ` Darren Hart
2018-08-06 11:36 ` Mihai Donțu
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=20180620233736.GA3250@fury \
--to=dvhart@infradead.org \
--cc=Mario.Limonciello@dell.com \
--cc=andy@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.dontu@gmail.com \
--cc=platform-driver-x86@vger.kernel.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