From: Soeren Moch <smoch@web.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Arnd Bergmann <arnd@arndb.de>,
USB list <linux-usb@vger.kernel.org>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-mm@kvack.org,
Kernel development list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] USB: EHCI: fix for leaking isochronous data
Date: Thu, 14 Mar 2013 21:51:11 +0100 [thread overview]
Message-ID: <5142383F.6010001@web.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1303141630550.1194-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On 14.03.2013 21:32, Alan Stern wrote:
> On Thu, 14 Mar 2013, Soeren Moch wrote:
>
>>>> I added a debug message to
>>>> drivers/usb/host/ehci-sched.c:itd_urb_transaction() to log the
>>>> allocation flags, see log below.
>>>
>>> But it looks like you didn't add a message to end_free_itds(), so we
>>> don't know when the memory gets deallocated. And you didn't print out
>>> the values of urb, num_itds, and i, or the value of itd (so we can
>>> match up allocations against deallocations).
>>
>> OK, I will implement this more detailed logging. But with several
>> allocations per second and runtime of several hours this will result in
>> a very long logfile.
>
> If the memory really is being leaked here in some sort of systematic
> way, we may be able to see it in your debugging output after a few
> seconds.
>
OK, here are the first seconds of the log. But the buffer exhaustion
usually occurs after several hours of runtime...
Soeren Moch
[-- Attachment #2: syslog.gz --]
[-- Type: application/x-gzip, Size: 24383 bytes --]
next prev parent reply other threads:[~2013-03-14 20:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1302211337580.1529-100000@iolanthe.rowland.org>
2013-03-10 18:45 ` [PATCH] USB: EHCI: fix for leaking isochronous data Soeren Moch
2013-03-10 20:59 ` Alan Stern
2013-03-14 18:48 ` Soeren Moch
2013-03-14 20:22 ` Soeren Moch
2013-03-14 20:32 ` Alan Stern
2013-03-14 20:51 ` Soeren Moch [this message]
2013-03-14 21:33 ` Alan Stern
2013-03-15 0:00 ` Soeren Moch
2013-03-15 14:30 ` Alan Stern
2013-03-16 2:10 ` Soeren Moch
2013-03-16 17:39 ` Alan Stern
2013-03-17 16:56 ` Soeren Moch
2013-03-17 17:36 ` Alan Stern
2013-03-17 17:39 ` Alan Stern
2013-03-21 17:04 ` Soeren Moch
2013-03-21 17:33 ` Jason Cooper
2013-03-21 19:10 ` Arnd Bergmann
2013-03-21 19:34 ` Michael Trimarchi
2013-03-21 21:52 ` Soeren Moch
2013-03-21 21:06 ` Alan Stern
2013-03-21 21:12 ` Alan Stern
2013-03-21 21:20 ` Andrew Lunn
2013-03-21 22:16 ` Soeren Moch
2013-03-22 14:24 ` Alan Stern
2013-03-21 21:45 ` Soeren Moch
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=5142383F.6010001@web.de \
--to=smoch@web.de \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stern@rowland.harvard.edu \
/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).