From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: guido@kiener-muenchen.de
Cc: Oliver Neukum <oneukum@suse.com>, linux-usb@vger.kernel.org
Subject: fixes for ioctl() of usbtmc in testing tree
Date: Mon, 24 Sep 2018 15:09:17 +0200 [thread overview]
Message-ID: <20180924130917.GA19703@kroah.com> (raw)
On Mon, Sep 24, 2018 at 12:20:42PM +0000, guido@kiener-muenchen.de wrote:
>
> Zitat von Oliver Neukum <oneukum@suse.com>:
>
> > On Mo, 2018-09-24 at 10:56 +0000, guido@kiener-muenchen.de wrote:
> > > Zitat von Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> > >
> > > > On Mon, Sep 24, 2018 at 11:24:10AM +0200, Oliver Neukum wrote:
> > > > > Hi,
> > > > >
> > > > > how should I mark fixes intended for the testing branch?
> > > > > I got one for the usbtmc driver.
> > > >
> > > > Just send it like normal. You can do a "Fixes:" tag with the sha1, that
> > > > should be fine. I need to push out my testing branch now, 0-day seems
> > > > to be stalled :(
> > > >
> > >
> > > Big sorry! There is a superflous kmalloc line 1270 til 1272.
> > > Shall I send the fix?
> >
> > Damn. That is the same allocation repeated, not a reuse of the buffer.
> > I'll resend. There is also a leak in the error case.
> >
>
> I do not see a leak in the error case. kfree(NULL) should be ok.
> Sorry, I referred the line 1270 to the mail of Dan Carpenter. I mean the
> lines:
>
> diff --git a/drivers/usb/class/usbtmc.c b/drivers/usb/class/usbtmc.c
> index 0fcb81a1399b..dfbcf418dad7 100644
> --- a/drivers/usb/class/usbtmc.c
> +++ b/drivers/usb/class/usbtmc.c
> @@ -1895,10 +1895,6 @@ static int usbtmc_ioctl_request(struct
> usbtmc_device_data *data,
> if (res)
> return -EFAULT;
>
> - buffer = kmalloc(request.req.wLength, GFP_KERNEL);
> - if (!buffer)
> - return -ENOMEM;
> -
> if (request.req.wLength > USBTMC_BUFSIZE)
> return -EMSGSIZE;
>
> @Oliver: Where do send (resend) the fix? Is this an official fix or
> do you just fix your internal build system?
> And I still have to make an official fix, isn't it?
Yes, you need to send a "real" patch for anyone to be able to pick it
up.
thanks,
greg k-h
next reply other threads:[~2018-09-24 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 13:09 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-28 16:26 fixes for ioctl() of usbtmc in testing tree Greg Kroah-Hartman
2018-09-28 8:30 Guido Kiener
2018-09-24 12:20 Guido Kiener
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=20180924130917.GA19703@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=guido@kiener-muenchen.de \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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;
as well as URLs for NNTP newsgroup(s).