From: Greg KH <gregkh@linuxfoundation.org>
To: ameynarkhede03@gmail.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gdm724x: Fix DMA from stack
Date: Tue, 9 Feb 2021 18:40:44 +0100 [thread overview]
Message-ID: <YCLJHNvKhiMJmTP8@kroah.com> (raw)
In-Reply-To: <20210209145415.29609-1-ameynarkhede03@gmail.com>
On Tue, Feb 09, 2021 at 08:24:15PM +0530, ameynarkhede03@gmail.com wrote:
> From: Amey Narkhede <ameynarkhede03@gmail.com>
>
> Stack allocated buffers cannot be used for DMA
> on all architectures so allocate usbdev buffer
> using kmalloc().
>
> Signed-off-by: Amey Narkhede <ameynarkhede03@gmail.com>
> ---
> drivers/staging/gdm724x/gdm_usb.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gdm724x/gdm_usb.c b/drivers/staging/gdm724x/gdm_usb.c
> index dc4da66c3..50dc463d4 100644
> --- a/drivers/staging/gdm724x/gdm_usb.c
> +++ b/drivers/staging/gdm724x/gdm_usb.c
> @@ -56,7 +56,7 @@ static int gdm_usb_recv(void *priv_dev,
>
> static int request_mac_address(struct lte_udev *udev)
> {
> - u8 buf[16] = {0,};
> + u8 *buf;
> struct hci_packet *hci = (struct hci_packet *)buf;
> struct usb_device *usbdev = udev->usbdev;
> int actual;
> @@ -66,6 +66,10 @@ static int request_mac_address(struct lte_udev *udev)
> hci->len = gdm_cpu_to_dev16(udev->gdm_ed, 1);
> hci->data[0] = MAC_ADDRESS;
>
> + buf = kmalloc(16, GFP_KERNEL);
> + if (!buf)
> + return -ENOMEM;
> +
This is great, but you just added a build warning, which implies that
the patch is incorrect.
You also have a memory leak here, which is not acceptable :(
thanks,
greg k-h
next prev parent reply other threads:[~2021-02-09 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 14:54 ameynarkhede03
2021-02-09 17:22 ` kernel test robot
2021-02-09 17:40 ` Greg KH [this message]
2021-02-09 19:35 ` Amey Narkhede
2021-02-09 18:19 ` Dan Carpenter
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=YCLJHNvKhiMJmTP8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ameynarkhede03@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®