From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751413AbdGRIIo (ORCPT <rfc822;w@1wt.eu>);
        Tue, 18 Jul 2017 04:08:44 -0400
Received: from regular1.263xmail.com ([211.150.99.131]:45920 "EHLO
        regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751340AbdGRIIl (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 18 Jul 2017 04:08:41 -0400
X-263anti-spam: KSV:0;BIG:0;
X-MAIL-GRAY: 0
X-MAIL-DELIVERY: 1
X-KSVirus-check: 0
X-ADDR-CHECKED4: 1
X-ABS-CHECKED: 1
X-SKE-CHECKED: 1
X-ANTISPAM-LEVEL: 2
X-RL-SENDER: jeffy.chen@rock-chips.com
X-FST-TO: oneukum@suse.com
X-SENDER-IP: 103.29.142.67
X-LOGIN-NAME: jeffy.chen@rock-chips.com
X-UNIQUE-TAG: <a83a900cefc0011c7e0c4d5bf728ba1a>
X-ATTACHMENT-NUM: 0
X-DNS-TYPE: 0
Message-ID: <596DC200.1080006@rock-chips.com>
Date: Tue, 18 Jul 2017 16:08:32 +0800
From: jeffy <jeffy.chen@rock-chips.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20130126 Thunderbird/19.0
MIME-Version: 1.0
To: Oliver Neukum <oneukum@suse.com>,
        Marcel Holtmann <marcel@holtmann.org>
CC: linux-kernel@vger.kernel.org, xiyou.wangcong@gmail.com,
        briannorris@chromium.org, dianders@chromium.org,
        Johan Hedberg <johan.hedberg@gmail.com>,
        "Gustavo F. Padovan" <gustavo@padovan.org>,
        linux-bluetooth@vger.kernel.org
Subject: Re: [RFC PATCH v2] Bluetooth: btusb: Fix memory leak in play_deferred
References: <1500343579-9831-1-git-send-email-jeffy.chen@rock-chips.com>  <6E21F79E-93AA-4461-BA6B-67715501714F@holtmann.org> <1500363015.16072.5.camel@suse.com>
In-Reply-To: <1500363015.16072.5.camel@suse.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Oliver,

On 07/18/2017 03:30 PM, Oliver Neukum wrote:
> Am Dienstag, den 18.07.2017, 08:44 +0200 schrieb Marcel Holtmann:
>>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>>> index 0d533b2..a22a08b 100644
>>> --- a/drivers/bluetooth/btusb.c
>>> +++ b/drivers/bluetooth/btusb.c
>>> @@ -3260,19 +3260,33 @@ static int btusb_suspend(struct usb_interface *intf, pm_message_t message)
>>>         return 0;
>>> }
>>>
>>> +static void btusb_deferred_tx_complete(struct urb *urb)
>>> +{
>>> +     btusb_tx_complete(urb);
>>> +     usb_free_urb(urb);
>>> +}
>>> +
>>> static void play_deferred(struct btusb_data *data)
>>> {
>>>         struct urb *urb;
>>>         int err;
>>>
>>>         while ((urb = usb_get_from_anchor(&data->deferred))) {
>>> +             /* Add a hook to free urb after completed */
>>> +             urb->complete = btusb_deferred_tx_complete;
>>> +
>>>                 err = usb_submit_urb(urb, GFP_ATOMIC);
>>> -             if (err < 0)
>>> -                     break;
>>> +             if (err < 0) {
>>> +                     if (err != -EPERM && err != -ENODEV)
>>> +                             BT_ERR("%s urb %p submission failed (%d)",
>>> +                                    data->hdev->name, urb, -err);
>>> +                     kfree(urb->setup_packet);
>>> +                     usb_free_urb(urb);
>>> +                     continue;
>>> +             }
>>>
>>>                 data->tx_in_flight++;
>>>         }
>>> -     usb_scuttle_anchored_urbs(&data->deferred);
>>> }
>>
>> can I get an ack from you on this one?
>
> Hi,
>
> I am afraid not. We cannot silently drop one part of a transmission.
> I am afraid that the correct algorithm, if we encounter an error at
> that stage, is to abort the operation and report an error.
>
so i should break the loop when error happens right?

and i uploaded 2 version of patches, which one do you prefer to go on?
> 	Regards
> 		Oliver
>
>
>
>