From: Amey Narkhede <ameynarkhede03@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: gdm724x: Fix DMA from stack
Date: Wed, 10 Feb 2021 21:06:21 +0530 [thread overview]
Message-ID: <20210210153621.3nmwsegn5a7mb5v5@archlinux> (raw)
In-Reply-To: <20210210151924.GA20820@kadam>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
On 21/02/10 06:19PM, Dan Carpenter wrote:
> On Wed, Feb 10, 2021 at 08:31:33PM +0530, Amey Narkhede wrote:
> > On 21/02/10 03:55PM, Greg KH wrote:
> > > On Wed, Feb 10, 2021 at 07:55:12PM +0530, Amey Narkhede wrote:
> > > > Stack allocated buffers cannot be used for DMA
> > > > on all architectures so allocate hci_packet buffer
> > > > using kmalloc.
> > > >
> > > > Signed-off-by: Amey Narkhede <ameynarkhede03@gmail.com>
> > > > ---
> > > > Changes in v3:
> > > > - Remove superfluous buf pointer
> > > > - Reduce size of allocation of hci_packet to match number of
> > > > bytes used for DMA
> > > >
> > > > drivers/staging/gdm724x/gdm_usb.c | 10 +++++++---
> > > > 1 file changed, 7 insertions(+), 3 deletions(-)
> > > >
> > > > diff --git a/drivers/staging/gdm724x/gdm_usb.c b/drivers/staging/gdm724x/gdm_usb.c
> > > > index dc4da66c3..80c58a3ef 100644
> > > > --- a/drivers/staging/gdm724x/gdm_usb.c
> > > > +++ b/drivers/staging/gdm724x/gdm_usb.c
> > > > @@ -56,20 +56,24 @@ 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;
> > > > + struct hci_packet *hci;
> > > > struct usb_device *usbdev = udev->usbdev;
> > > > int actual;
> > > > int ret = -1;
> > > >
> > > > + hci = kmalloc(5, GFP_KERNEL);
> > >
> > > Why "5" and not:
> > > hci = kmalloc(sizeof(*hci), GFP_KERNEL);
>
> 5 is correct and sizeof(*hci) is 4. The hci struct ends in a zero
> element array. You could do:
>
> hci = kmalloc(struct_size(hci, data, 1), GFP_KERNEL);
>
> I'm not sure it's more readable. But you still will have to resend
> because the patch passes "&hci" to usb_bulk_msg() instead of "hci" so it
> will corrupt memory.
>
> I always encourage people to write the patch and then sit on it over
> night and send it the next day.
>
> regards,
> dan carpenter
>
Yes I was about to send patch with kmalloc(sizeof(*hci) + sizeof(u8)).
Now I'll take your advice and send the patch tomorrow.
Thanks,
Amey
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-10 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 14:25 [PATCH v3] staging: gdm724x: Fix DMA from stack Amey Narkhede
2021-02-10 14:55 ` Greg KH
2021-02-10 15:01 ` Amey Narkhede
2021-02-10 15:19 ` Dan Carpenter
2021-02-10 15:36 ` Amey Narkhede [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=20210210153621.3nmwsegn5a7mb5v5@archlinux \
--to=ameynarkhede03@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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