From: Greg KH <gregkh@linuxfoundation.org>
To: ameynarkhede03@gmail.com
Cc: dan.carpenter@oracle.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: gdm724x: Fix DMA from stack
Date: Tue, 9 Feb 2021 20:52:22 +0100 [thread overview]
Message-ID: <YCLn9j60wD2/RG9K@kroah.com> (raw)
In-Reply-To: <20210209193147.558514-1-ameynarkhede03@gmail.com>
On Wed, Feb 10, 2021 at 01:01:47AM +0530, ameynarkhede03@gmail.com wrote:
> From: Amey Narkhede <ameynarkhede03@gmail.com>
>
> Stack allocated buffers cannot be used for DMA
> on all architectures so allocate hci_packet buffer
> using kzalloc().
>
> Signed-off-by: Amey Narkhede <ameynarkhede03@gmail.com>
> ---
> drivers/staging/gdm724x/gdm_usb.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/gdm724x/gdm_usb.c b/drivers/staging/gdm724x/gdm_usb.c
> index dc4da66c3..c4a9b90c5 100644
> --- a/drivers/staging/gdm724x/gdm_usb.c
> +++ b/drivers/staging/gdm724x/gdm_usb.c
> @@ -56,11 +56,15 @@ static int gdm_usb_recv(void *priv_dev,
>
> static int request_mac_address(struct lte_udev *udev)
> {
> - u8 buf[16] = {0,};
> - struct hci_packet *hci = (struct hci_packet *)buf;
> + u8 *buf;
> + struct hci_packet *hci;
> struct usb_device *usbdev = udev->usbdev;
> int actual;
> int ret = -1;
> + buf = kzalloc(16, GFP_KERNEL);
> + if (!buf)
> + return -ENOMEM;
> + hci = (struct hci_packet *)buf;
>
> hci->cmd_evt = gdm_cpu_to_dev16(udev->gdm_ed, LTE_GET_INFORMATION);
> hci->len = gdm_cpu_to_dev16(udev->gdm_ed, 1);
> @@ -70,6 +74,7 @@ static int request_mac_address(struct lte_udev *udev)
> &actual, 1000);
>
> udev->request_mac_addr = 1;
> + kfree(buf);
>
> return ret;
> }
> --
> 2.30.0
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- Your patch contains warnings and/or errors noticed by the
scripts/checkpatch.pl tool.
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/SubmittingPatches for what needs to be done
here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
next prev parent reply other threads:[~2021-02-09 23:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 19:31 [PATCH v2] staging: gdm724x: Fix DMA from stack ameynarkhede03
2021-02-09 19:52 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-10 8:01 Amey Narkhede
2021-02-10 8:06 ` Greg KH
2021-02-10 8:58 ` Amey Narkhede
2021-02-10 9:04 ` Dan Carpenter
2021-02-10 10:48 ` Amey Narkhede
2021-02-10 9:09 ` Greg KH
2021-02-10 10:54 ` Amey Narkhede
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=YCLn9j60wD2/RG9K@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ameynarkhede03@gmail.com \
--cc=dan.carpenter@oracle.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