From: Julia Lawall <julia@diku.dk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] Eliminate double kfree
Date: Thu, 29 May 2008 17:57:50 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805291754480.26229@ask.diku.dk> (raw)
In-Reply-To: <20080529101012.ZZRA012@mailhub.coreip.homeip.net>
On Thu, 29 May 2008, Dmitry Torokhov wrote:
> Hi Julia,
>
> On Thu, May 29, 2008 at 03:05:07PM +0200, Julia Lawall wrote:
> > From: Julia Lawall <julia@diku.dk>
> >
> > The variable report is only non-NULL and non-freed in a small region of
> > code, so it should only be freed in error handling code that comes from
> > that region.
> >
>
> Thank you for your patch. There isn't a double-kfree though, as far
> as I can see.
There was a double free because the error handling at the end of the
function (for input_register_device) would fall through to the
kfree(report) under err_free_devs, even though report is already freed at
that point.
Your solution does indeed look more elegant, and seems to preserve the
semantics of the original code.
julia
> Because we need to free the report in both success and
> failure cases the error handling is a bit unwieldy I agree. I don't
> want to apply your patch though because I don't like when we bypass
> parts of error handling path that weren't bypassed if we aborted
> earlier, if you follow me.
>
> What do you think about the patch below?
>
> --
> Dmitry
>
> Input: gtco - clean up error handling in gtco_probe
>
> Thanks to Julia Lawall for noticing ugliness.
>
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> drivers/input/tablet/gtco.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> Index: linux/drivers/input/tablet/gtco.c
> ===================================================================
> --- linux.orig/drivers/input/tablet/gtco.c
> +++ linux/drivers/input/tablet/gtco.c
> @@ -830,7 +830,7 @@ static int gtco_probe(struct usb_interfa
> struct gtco *gtco;
> struct input_dev *input_dev;
> struct hid_descriptor *hid_desc;
> - char *report = NULL;
> + char *report;
> int result = 0, retry;
> int error;
> struct usb_endpoint_descriptor *endpoint;
> @@ -916,12 +916,16 @@ static int gtco_probe(struct usb_interfa
> le16_to_cpu(hid_desc->wDescriptorLength),
> 5000); /* 5 secs */
>
> - if (result == le16_to_cpu(hid_desc->wDescriptorLength))
> + dbg("usb_control_msg result: %d", result);
> + if (result == le16_to_cpu(hid_desc->wDescriptorLength)) {
> + parse_hid_report_descriptor(gtco, report, result);
> break;
> + }
> }
>
> + kfree(report);
> +
> /* If we didn't get the report, fail */
> - dbg("usb_control_msg result: :%d", result);
> if (result != le16_to_cpu(hid_desc->wDescriptorLength)) {
> err("Failed to get HID Report Descriptor of size: %d",
> hid_desc->wDescriptorLength);
> @@ -929,12 +933,6 @@ static int gtco_probe(struct usb_interfa
> goto err_free_urb;
> }
>
> - /* Now we parse the report */
> - parse_hid_report_descriptor(gtco, report, result);
> -
> - /* Now we delete it */
> - kfree(report);
> -
> /* Create a device file node */
> usb_make_path(gtco->usbdev, gtco->usbpath, sizeof(gtco->usbpath));
> strlcat(gtco->usbpath, "/input0", sizeof(gtco->usbpath));
> @@ -988,7 +986,6 @@ static int gtco_probe(struct usb_interfa
> usb_buffer_free(gtco->usbdev, REPORT_MAX_SIZE,
> gtco->buffer, gtco->buf_dma);
> err_free_devs:
> - kfree(report);
> input_free_device(input_dev);
> kfree(gtco);
> return error;
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-05-29 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 13:05 [PATCH 2/2] Eliminate double kfree Julia Lawall
2008-05-29 15:33 ` Dmitry Torokhov
2008-05-29 15:57 ` Julia Lawall [this message]
2008-05-29 16:14 ` Dmitry Torokhov
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=Pine.LNX.4.64.0805291754480.26229@ask.diku.dk \
--to=julia@diku.dk \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).