From: Dave Jones <davej@codemonkey.org.uk>
To: netdev@vger.kernel.org
Subject: huge failed atomic allocation in dccp.
Date: Sat, 17 May 2008 18:20:27 -0400 [thread overview]
Message-ID: <20080517222027.GB31440@codemonkey.org.uk> (raw)
This strikes me as somewhat bizarre..
modprobe: page allocation failure. order:10, mode:0x20
Pid: 10505, comm: modprobe Not tainted 2.6.25-14.fc9.x86_64 #1
Call Trace:
[<ffffffff8107ee4c>] __alloc_pages+0x351/0x371
[<ffffffff8109fc0d>] ? sysfs_slab_alias+0x41/0x81
[<ffffffff81097d90>] alloc_pages_current+0x100/0x109
[<ffffffff8107e1ac>] __get_free_pages+0xe/0x4d
[<ffffffff881010bd>] :dccp:dccp_init+0xbd/0x3a5
[<ffffffff81057627>] sys_init_module+0x193f/0x1a87
[<ffffffff810a4c90>] ? do_sync_read+0xe7/0x12d
[<ffffffff81205eab>] ? release_sock+0x0/0xaf
[<ffffffff8106d543>] ? audit_syscall_entry+0x126/0x15a
[<ffffffff81013073>] ? syscall_trace_enter+0xb5/0xb9
[<ffffffff8100c052>] tracesys+0xd5/0xda
An order 10 GFP_ATOMIC allocation failing shouldn't really be surprising.
The hash sizing in dccp_init seems to cope with this situation
by trying successively smaller values, but this will cause
spew to the logs whilst it's doing that.
Dave
--
http://www.codemonkey.org.uk
reply other threads:[~2008-05-17 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080517222027.GB31440@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=netdev@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).