From: Peter Chen <peter.chen@freescale.com>
To: Felipe Tonello <eu@felipetonello.com>
Cc: USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>,
"Andrzej Pietrasiewicz" <andrzej.p@samsung.com>
Subject: Re: [PATCH 3/3] usb: gadget: f_midi: free request when usb_ep_queue fails
Date: Thu, 24 Sep 2015 09:20:02 +0800 [thread overview]
Message-ID: <20150924012001.GB10369@shlinux2> (raw)
In-Reply-To: <CAGrhNMyaNjtZYErKY=OK5PJ=HiYrw1=D1nGMH+AKNw01n3KVYg@mail.gmail.com>
On Wed, Sep 23, 2015 at 12:40:46PM +0100, Felipe Tonello wrote:
> Hi Peter,
>
> On Wed, Sep 23, 2015 at 8:09 AM, Peter Chen <peter.chen@freescale.com> wrote:
> > On Tue, Sep 22, 2015 at 07:59:10PM +0100, Felipe F. Tonello wrote:
> >> This fix a memory leak that will occur in this case.
> >>
> >> Signed-off-by: Felipe F. Tonello <eu@felipetonello.com>
> >> ---
> >> drivers/usb/gadget/function/f_midi.c | 4 +++-
> >> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/usb/gadget/function/f_midi.c b/drivers/usb/gadget/function/f_midi.c
> >> index e92aff5..e6a114b 100644
> >> --- a/drivers/usb/gadget/function/f_midi.c
> >> +++ b/drivers/usb/gadget/function/f_midi.c
> >> @@ -550,9 +550,11 @@ static void f_midi_transmit(struct f_midi *midi, struct usb_request *req)
> >> int err;
> >>
> >> err = usb_ep_queue(ep, req, GFP_ATOMIC);
> >> - if (err < 0)
> >> + if (err < 0) {
> >> ERROR(midi, "%s queue req: %d\n",
> >> midi->in_ep->name, err);
> >> + free_ep_req(ep, req);
> >> + }
> >> } else {
> >> free_ep_req(ep, req);
> >> }
> >> --
> >> 2.1.4
> >>
> >
> > I may know your problem, current midi library, alsa and this driver
> > allow device sends as much data as possible, but without block the
> > sending until host reads data, it only allocates the request buffer
> > (using midi_alloc_ep_req), but without free, so after you send
> > enough data, it is out of memory.
>
> Yes. Also there is the case where the usb cable is not conected, thus
> failing to hardware enqueue the request, causing a memory leak on this
> request.
>
If the usb cable is not connected, the related endpoints should be
not enabled. Would you really observe enqueue the request without
cable connected?
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2015-09-24 1:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 18:59 [PATCH 1/3] usb: chipidea: core: fix when building without CONFIG_PM support Felipe F. Tonello
2015-09-22 18:59 ` [PATCH 2/3] usb: gadget: f_midi: free usb request when done Felipe F. Tonello
2015-09-22 21:14 ` Felipe Balbi
2015-09-23 3:10 ` Peter Chen
2015-09-23 11:47 ` Felipe Tonello
2015-09-23 14:30 ` Alan Stern
2015-09-23 14:47 ` Felipe Tonello
2015-09-22 18:59 ` [PATCH 3/3] usb: gadget: f_midi: free request when usb_ep_queue fails Felipe F. Tonello
2015-09-22 21:17 ` Felipe Balbi
2015-09-23 7:09 ` Peter Chen
2015-09-23 11:40 ` Felipe Tonello
2015-09-24 1:20 ` Peter Chen [this message]
2015-09-25 8:27 ` Felipe Tonello
2015-09-25 9:02 ` Peter Chen
2015-09-25 10:25 ` Felipe Tonello
2015-09-22 21:12 ` [PATCH 1/3] usb: chipidea: core: fix when building without CONFIG_PM support Felipe Balbi
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=20150924012001.GB10369@shlinux2 \
--to=peter.chen@freescale.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=eu@felipetonello.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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