From: Markus Rechberger <mrechberger@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: USBFS Memory allocation Bug
Date: Wed, 10 Mar 2010 00:32:42 +0100 [thread overview]
Message-ID: <d9def9db1003091532icb671efy48b30185b86effcb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003091729320.1693-100000@iolanthe.rowland.org>
On Tue, Mar 9, 2010 at 11:31 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Tue, 9 Mar 2010, Markus Rechberger wrote:
>
>> Hi,
>>
>> I just stumbled around following issue:
>>
>> [275835.163502] Pid: 14298, comm: mediasrv Not tainted 2.6.33 #7
>> [275835.163505] Call Trace:
>> [275835.163514] [<ffffffff810df7a6>] __alloc_pages_nodemask+0x5b6/0x700
>> [275835.163520] [<ffffffff8110c667>] alloc_pages_current+0x87/0xd0
>> [275835.163525] [<ffffffff810dcf79>] __get_free_pages+0x9/0x50
>> [275835.163529] [<ffffffff81114f2b>] __kmalloc+0x13b/0x1f0
>> [275835.163535] [<ffffffff813a18ef>] proc_do_submiturb+0x2ff/0x9d0
>> [275835.163539] [<ffffffff813a26b9>] usbdev_do_ioctl+0x6f9/0x14a0
>
> The mediasrv program tried to allocate more memory than was available.
> It's unfortunate but it's not a bug.
>
Yes, 'unfortunate' is what bothers me about this, it can only be
around 198kbyte what the app can try to request (everything else will
fail internally).
The system has 4 gig ram, around 1 gig was not allocated (according to
free). not sure but I guess the pool where kmalloc tried to get the
memory from was out of memory, at least the OOM manager was not active
at all either and the rest of the system was more or less running
smoothly at this time.
Markus
next prev parent reply other threads:[~2010-03-09 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 21:09 USBFS Memory allocation Bug Markus Rechberger
2010-03-09 22:31 ` Alan Stern
2010-03-09 23:32 ` Markus Rechberger [this message]
2010-03-10 3:13 ` Alan Stern
2010-03-10 9:33 ` Markus Rechberger
2010-03-10 15:04 ` Alan Stern
2010-03-10 13:57 ` Mel Gorman
2010-03-10 15:16 ` Alan Stern
2010-03-10 15:21 ` Mel Gorman
2010-03-10 15:49 ` Alan Stern
2010-03-10 15:55 ` Mel Gorman
2010-03-11 16:56 ` Alan Stern
2010-03-14 23:31 ` Andrew Morton
2010-03-15 9:36 ` Mel Gorman
2010-03-15 13:57 ` Alan Stern
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=d9def9db1003091532icb671efy48b30185b86effcb@mail.gmail.com \
--to=mrechberger@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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