Toralf Förster | 7 May 2013 19:19
Picon
Picon

[uml-user] [info] syscalls mmap and mremap no longer fails w/ SLUB

Since today both syscalls seems to work fine with SLUB and guest kernel
linux-v3.9-10998-g1b9b170 at a stable Getnoo 32 bit, now just these 4
are still forcing kernel bugs if stressed with trinity :

-x mount -x request_key -x add_key -x keyctl

(me just re-tested both b/c I saw a lot af SLAB/SLUB related merges into
mainline but ofc I'm unsure when those 2 were fixed).

--

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
Toralf Förster | 6 May 2013 22:47
Picon
Picon

[uml-user] BUG: spinlock recursion 3.9.0-10520-gf8cf7ba

The following BUG was triggered by trinity on an UML guest with kernel
version 3.9.0-10520-gf8cf7ba and host kernel 3.9, both are stable 32 bit Gentoo Linux.

Is this UML specific or worth to be reported to LKML too ?

2013-05-06T22:26:32.091+02:00 trinity kernel: BUG: spinlock recursion on CPU#0, rngd/916
2013-05-06T22:26:32.091+02:00 trinity kernel: lock: 0x847146c, .magic: dead4ead, .owner: rngd/916,
.owner_cpu: 0
2013-05-06T22:26:32.091+02:00 trinity kernel: CPU: 0 PID: 916 Comm: rngd Not tainted
3.9.0-10520-gf8cf7ba #19
2013-05-06T22:26:32.091+02:00 trinity kernel: 40827990 408279c0 083986e6 0843260c 0847146c
dead4ead 4181c7b0 00000394 
2013-05-06T22:26:32.091+02:00 trinity kernel: 00000000 40824000 0847146c 084324ea 408279d0
08398708 0847146c 00000008 
2013-05-06T22:26:32.091+02:00 trinity kernel: 408279f0 0828a2de 080a5975 08479940 40824000
00000000 00000008 00000000 40827964:  [<08062d4f>] show_stack+0xcf/0x100
2013-05-06T22:26:32.091+02:00 trinity kernel: 40827988:  [<083985d5>] dump_stack+0x26/0x28
2013-05-06T22:26:32.091+02:00 trinity kernel: 40827998:  [<083986e6>] spin_dump+0xa5/0xac
2013-05-06T22:26:32.091+02:00 trinity kernel: 408279c4:  [<08398708>] spin_bug+0x1b/0x1f
2013-05-06T22:26:32.091+02:00 trinity kernel: 408279d4:  [<0828a2de>] do_raw_spin_lock+0x4e/0x100
2013-05-06T22:26:32.095+02:00 trinity kernel: 408279f4:  [<0839acc1>] _raw_spin_lock+0x11/0x20
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a00:  [<08062872>] sigio_lock+0x12/0x20
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a0c:  [<080735c4>] add_sigio_fd+0x14/0x100
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a34:  [<08060d7a>] reactivate_fd+0x6a/0x80
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a50:  [<080627e7>] sigio_interrupt+0x37/0x40
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a68:  [<080ca7bf>] handle_irq_event_percpu+0x2f/0x150
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827a98:  [<080ca91a>] handle_irq_event+0x3a/0x60
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827ab4:  [<080ccd60>] handle_edge_irq+0xe0/0x110
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827ac8:  [<080ca16b>] generic_handle_irq+0x2b/0x30
2013-05-06T22:26:32.095+02:00 trinity kernel: 40827ad8:  [<08060e75>] do_IRQ+0x25/0x40
(Continue reading)

Toralf Förster | 30 Apr 2013 22:22
Picon
Picon

[uml-user] fuzzying UML with SLAB gives sometimes a page allocation failure

While playing with kernel 3.9 (host) and current git kernel linux-v3.9-3618-g490b364 (guest)
and running trinity on the guest I got after a longer run of trinity
syslog messages at the guest as seen below.

I get these only if I compiled the UML guest kernel with SLAB (and not with SLUB).
But b/c under SLUB I cannot test the 6 syscalls mremap, mmap, mount, add_key, request_key and keyctl
(those are known to fail immediately and tainting the guest kernel) I've no clue whether the page
allocation failure is related to those syscalls or to SLAB itself.

I'll run trinity excluding those 6 syscalls but that needs time.

Both host and guest are 32 bit stable Gentoo, the victim files + directories for trinity
are located on a directory mounted on the guest via hostfs and nfsv4 respectively.


2013-04-30T22:06:34.737+02:00 trinity kernel: kworker/0:2: page allocation failure: order:0, mode:0x20
2013-04-30T22:06:34.737+02:00 trinity kernel: 40803664:  [<0836ff38>] dump_stack+0x22/0x24
2013-04-30T22:06:34.737+02:00 trinity kernel: 4080367c:  [<080cf521>] warn_alloc_failed+0xf1/0x110
2013-04-30T22:06:34.737+02:00 trinity kernel: 408036b0:  [<080d1d2d>] __alloc_pages_nodemask+0x6fd/0x750
2013-04-30T22:06:34.737+02:00 trinity kernel: 4080373c:  [<082a3766>] __netdev_alloc_frag+0x66/0x140
2013-04-30T22:06:34.737+02:00 trinity kernel: 40803768:  [<082a3f7f>] __netdev_alloc_skb+0x3f/0xd0
2013-04-30T22:06:34.737+02:00 trinity kernel: 4080378c:  [<08068ff5>] uml_net_rx+0x35/0x100
2013-04-30T22:06:34.737+02:00 trinity kernel: 408037ac:  [<080691ef>] uml_net_interrupt+0x1f/0x90
2013-04-30T22:06:34.737+02:00 trinity kernel: 408037c4:  [<080c679f>] handle_irq_event_percpu+0x2f/0x150
2013-04-30T22:06:34.737+02:00 trinity kernel: 408037f4:  [<080c68e7>] handle_irq_event+0x27/0x40
2013-04-30T22:06:34.743+02:00 trinity kernel: 40803808:  [<080c8bc0>] handle_edge_irq+0xd0/0x100
2013-04-30T22:06:34.743+02:00 trinity kernel: 40803818:  [<080c6158>] generic_handle_irq+0x28/0x30
2013-04-30T22:06:34.743+02:00 trinity kernel: 40803828:  [<08060e55>] do_IRQ+0x25/0x40
2013-04-30T22:06:34.743+02:00 trinity kernel: 40803838:  [<08060ed5>] sigio_handler+0x65/0x80
2013-04-30T22:06:34.743+02:00 trinity kernel: 40803850:  [<080739f8>] sig_handler_common+0xb8/0xe0
(Continue reading)

Toralf Förster | 26 Apr 2013 18:26
Picon
Picon

[uml-user] derive assigned DHCP address of a tap device

After I started an UML instance (configured to get a DHCP address from
the host where dnsmasq acts as a DHCP server) I'd later like to derive
which ip address the appropriate TAP device was assigned too.

Currently I'm at a loss how to do this.

--

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
Toralf Förster | 14 Apr 2013 15:09
Picon
Picon

[uml-user] trinity triggers (a different ?) madvise syscall issue: "BUG: Bad page map" and "BUG: Bad rss-counter"

The following issue at a guest kernel using current v3.9-rc6-186-g5b55d70 guest kernel
and 3.8.7 host kernel (both 32 bit Gentoo Linux) can repeatable be triggered:

2013-04-14T15:04:00.366+02:00 trinity kernel: BUG: Bad page map in process trinity-child3 
pte:0032a045 pmd:358ca1e1
2013-04-14T15:04:00.366+02:00 trinity kernel: page:09b29540 count:1 mapcount:-1 mapping:  (null) index:0x0
2013-04-14T15:04:00.366+02:00 trinity kernel: page flags: 0x404(referenced|reserved)
2013-04-14T15:04:00.366+02:00 trinity kernel: addr:00100000 vm_flags:00060055 anon_vma:  (null)
mapping:  (null) index:100
2013-04-14T15:04:00.366+02:00 trinity kernel: vma->vm_ops->fault: special_mapping_fault+0x0/0x80
2013-04-14T15:04:00.366+02:00 trinity kernel: 3d8cfd20:  [<0836d3b8>] dump_stack+0x22/0x24
2013-04-14T15:04:00.366+02:00 trinity kernel: 3d8cfd38:  [<0836e796>] print_bad_pte+0x17b/0x197
2013-04-14T15:04:00.366+02:00 trinity kernel: 3d8cfd7c:  [<080e2918>] unmap_single_vma+0x268/0x430
2013-04-14T15:04:00.366+02:00 trinity kernel: 3d8cfddc:  [<080e30a4>] zap_page_range+0x74/0xb0
2013-04-14T15:04:00.366+02:00 trinity kernel: 3d8cfe10:  [<080e13ed>] sys_madvise+0x3bd/0x720
2013-04-14T15:04:00.367+02:00 trinity kernel: 3d8cfeac:  [<08064a92>] handle_syscall+0x82/0xb0
2013-04-14T15:04:00.367+02:00 trinity kernel: 3d8cfef4:  [<08076e6d>] userspace+0x46d/0x590
2013-04-14T15:04:00.367+02:00 trinity kernel: 3d8cffec:  [<080617bc>] fork_handler+0x6c/0x70
2013-04-14T15:04:00.367+02:00 trinity kernel: 3d8cfffc:  [<00000000>] 0x0
2013-04-14T15:04:00.367+02:00 trinity kernel:
2013-04-14T15:04:00.367+02:00 trinity kernel: Disabling lock debugging due to kernel taint
2013-04-14T15:04:00.367+02:00 trinity kernel: BUG: Bad page state in process trinity-child3  pfn:0032a
2013-04-14T15:04:00.367+02:00 trinity kernel: page:09b29540 count:0 mapcount:-1 mapping:  (null) index:0x0
2013-04-14T15:04:00.367+02:00 trinity kernel: page flags: 0x404(referenced|reserved)
2013-04-14T15:04:00.367+02:00 trinity kernel: 3d8cfcd8:  [<0836d3b8>] dump_stack+0x22/0x24
2013-04-14T15:04:00.369+02:00 trinity kernel: 3d8cfcf0:  [<080cee75>] bad_page+0xb5/0xe0
2013-04-14T15:04:00.369+02:00 trinity kernel: 3d8cfd0c:  [<080cef13>] free_pages_prepare+0x73/0xb0
2013-04-14T15:04:00.369+02:00 trinity kernel: 3d8cfd28:  [<080d033d>] free_hot_cold_page+0x1d/0x100
2013-04-14T15:04:00.369+02:00 trinity kernel: 3d8cfd50:  [<080d2cee>] __put_single_page+0x1e/0x30
2013-04-14T15:04:00.369+02:00 trinity kernel: 3d8cfd64:  [<080d2e17>] put_page+0x27/0x30
(Continue reading)

Toralf Förster | 11 Apr 2013 20:46
Picon
Picon

[uml-user] uml + SLAB + trinity triggers: WARNING: at mm/mmap.c:2702 exit_mmap+0x161/0x170()

Just for completeness, if SLAB is chosen (SLUB issues are already reported)
then with host kernel 3.8.6 and guest kernel 3.9-rc6-xxx and 32bit stable Gentoo Linux
both for host and guest sometimes that warning is chosen.
The tool trinity tries to avoid the syscall exit_group but that seems to be triggered nevertheless.

2013-04-11T20:38:20.925+02:00 trinity kernel: ------------[ cut here ]------------
2013-04-11T20:38:20.925+02:00 trinity kernel: WARNING: at mm/mmap.c:2702 exit_mmap+0x161/0x170()
2013-04-11T20:38:20.925+02:00 trinity kernel: 3ee73d90:  [<0836d388>] dump_stack+0x22/0x24
2013-04-11T20:38:20.925+02:00 trinity kernel: 3ee73da8:  [<0807f0da>] warn_slowpath_common+0x5a/0x80
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73dd0:  [<0807f1a3>] warn_slowpath_null+0x23/0x30
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73de0:  [<080e8ce1>] exit_mmap+0x161/0x170
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73e18:  [<0807ccd9>] mmput+0x39/0x90
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73e2c:  [<08083df0>] do_exit+0x2d0/0x820
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73e7c:  [<08084417>] do_group_exit+0x97/0xe0
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73ea0:  [<08084479>] sys_exit_group+0x19/0x20
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73eac:  [<08064a52>] handle_syscall+0x82/0xb0
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73ef4:  [<08076e2d>] userspace+0x46d/0x590
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73fec:  [<080617bc>] fork_handler+0x6c/0x70
2013-04-11T20:38:20.927+02:00 trinity kernel: 3ee73ffc:  [<00000000>] 0x0
2013-04-11T20:38:20.930+02:00 trinity kernel: 
2013-04-11T20:38:20.930+02:00 trinity kernel: ---[ end trace cba01caf050f6b66 ]---

--

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
(Continue reading)

Toralf Förster | 2 Apr 2013 21:50
Picon
Picon

[uml-user] trinity + SLUB + syscall [ mount, add_key, request_key, keyctl ] = WARNING: at mm/page_alloc.c:2386

Well,

fuzzying an UML (32 bit Gentoo Linux) system with SLUB for current git kernel 3.9-rc5-x gives
for the mentioned 4 syscalls very quickly a warning like the seen below.

What I (as usual) do not know, is, if these warnings are UML architecture specific
or if I should Cc: the LKML ?

2013-04-02T21:44:05.800+02:00 trinity kernel: ------------[ cut here ]------------
2013-04-02T21:44:05.800+02:00 trinity kernel: WARNING: at mm/page_alloc.c:2386 __alloc_pages_nodemask+0x153/0x750()
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfd14:  [<0836f888>] dump_stack+0x22/0x24
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfd2c:  [<0807f14a>] warn_slowpath_common+0x5a/0x80
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfd54:  [<0807f213>] warn_slowpath_null+0x23/0x30
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfd64:  [<080d03a3>] __alloc_pages_nodemask+0x153/0x750
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfdf0:  [<080d09c8>] __get_free_pages+0x28/0x50
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfe08:  [<080f9e0f>] __kmalloc_track_caller+0x3f/0x180
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfe30:  [<080dbee6>] memdup_user+0x26/0x70
2013-04-02T21:44:05.800+02:00 trinity kernel: 405dfe4c:  [<080dc0ee>] strndup_user+0x3e/0x60
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dfe68:  [<081190f0>] copy_mount_string+0x30/0x50
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dfe7c:  [<08119af2>] sys_mount+0x52/0xe0
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dfeac:  [<08064a92>] handle_syscall+0x82/0xb0
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dfef4:  [<08076edd>] userspace+0x46d/0x590
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dffec:  [<080617cc>] fork_handler+0x6c/0x70
2013-04-02T21:44:05.801+02:00 trinity kernel: 405dfffc:  [<5a5a5a5a>] 0x5a5a5a5a
2013-04-02T21:44:05.801+02:00 trinity kernel:
2013-04-02T21:44:05.801+02:00 trinity kernel: ---[ end trace c1c5349b53f54f0a ]---

or

2013-04-02T21:47:23.646+02:00 trinity kernel: ------------[ cut here ]------------
(Continue reading)

Toralf Förster | 1 Apr 2013 19:13
Picon
Picon

[uml-user] arbitrary kernel crash during stratup

Is the following back trace another example of  signal issue of UML :

(gdb) bt
#0  0x469fc920 in ?? ()
#1  0x08071656 in hard_handler (sig=138428456, si=0x840404c <cpu0_irqstack+76>, p=0x84040e0
<cpu0_irqstack+224>) at arch/um/os-Linux/signal.c:162
#2  <signal handler called>
#3  0x469fc920 in ?? ()
#4  0x08071656 in hard_handler (sig=138429736, si=0x840454c <cpu0_irqstack+1356>, p=0x84045e0
<cpu0_irqstack+1504>) at arch/um/os-Linux/signal.c:162   
#5  <signal handler called>
#6  0x469fc920 in ?? ()
#7  0x08071656 in hard_handler (sig=138431016, si=0x8404a4c <cpu0_irqstack+2636>, p=0x8404ae0
<cpu0_irqstack+2784>) at arch/um/os-Linux/signal.c:162
#8  <signal handler called>
#9  0x469fc920 in ?? ()
#10 0x08071656 in hard_handler (sig=138432296, si=0x8404f4c <cpu0_irqstack+3916>, p=0x8404fe0
<cpu0_irqstack+4064>) at arch/um/os-Linux/signal.c:162
#11 <signal handler called>
#12 0x469fc920 in ?? ()
#13 0x08071656 in hard_handler (sig=138433576, si=0x840544c <cpu0_irqstack+5196>, p=0x84054e0
<cpu0_irqstack+5344>) at arch/um/os-Linux/signal.c:162
#14 <signal handler called>
#15 0x469fc920 in ?? ()
#16 0x08071656 in hard_handler (sig=138434856, si=0x840594c <cpu0_irqstack+6476>, p=0x84059e0
<cpu0_irqstack+6624>) at arch/um/os-Linux/signal.c:162
#17 <signal handler called>
#18 0x469fc920 in ?? ()
#19 0x08071656 in hard_handler (sig=138436136, si=0x8405e4c <cpu0_irqstack+7756>, p=0x8405ee0
<cpu0_irqstack+7904>) at arch/um/os-Linux/signal.c:162
(Continue reading)

Toralf Förster | 17 Mar 2013 16:32
Picon
Picon

[uml-user] "BUG: spinlock" triggered by trinity fuzzing

with host kernel 3.8.3 and UML guest kernel 3.9-rc2-333-ge204378

/me wonders if this is UML specific or if I should Cc: lkml too ?

...
2013-03-17T16:16:17.942+01:00 trinity kernel: memdup_user: 2
2013-03-17T16:16:17.942+01:00 trinity kernel: memdup_user: 5
2013-03-17T16:16:21.831+01:00 trinity kernel: memdup_user: -14
2013-03-17T16:17:09.299+01:00 trinity kernel: memdup_user: 1
2013-03-17T16:17:55.762+01:00 trinity kernel: memdup_user: 4096
2013-03-17T16:18:23.474+01:00 trinity kernel: BUG: spinlock recursion on CPU#0, rngd/913
2013-03-17T16:18:23.474+01:00 trinity kernel: lock: 0x842d4ac, .magic: dead4ead, .owner: rngd/913,
.owner_cpu: 0
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d7984:  [<0835bea8>] dump_stack+0x22/0x24
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d799c:  [<0835e8dd>] spin_dump+0xa5/0xac
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d79c8:  [<0835e8ff>] spin_bug+0x1b/0x1f
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d79d8:  [<08285cae>] do_raw_spin_lock+0x4e/0x100
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d79f8:  [<083614c1>] _raw_spin_lock+0x11/0x20
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d7a04:  [<08061872>] sigio_lock+0x12/0x20
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d7a10:  [<080724a4>] add_sigio_fd+0x14/0x100
2013-03-17T16:18:23.474+01:00 trinity kernel: 386d7a38:  [<0805fd7a>] reactivate_fd+0x6a/0x80
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7a54:  [<080617e7>] sigio_interrupt+0x37/0x40
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7a6c:  [<080cc1af>] handle_irq_event_percpu+0x2f/0x150
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7a9c:  [<080cc30a>] handle_irq_event+0x3a/0x60
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7ab8:  [<080ce720>] handle_edge_irq+0xe0/0x110
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7acc:  [<080cbb5b>] generic_handle_irq+0x2b/0x30
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7adc:  [<0805fe75>] do_IRQ+0x25/0x40
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7aec:  [<0805fef5>] sigio_handler+0x65/0x80
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7b04:  [<08072d28>] sig_handler_common+0xb8/0xe0
2013-03-17T16:18:23.475+01:00 trinity kernel: 386d7d88:  [<08072c4b>] unblock_signals+0x4b/0x70
(Continue reading)

Han | 15 Mar 2013 05:39
Picon

[uml-user] kmalloc returns NULL during module init

Hi,

I am trying to build and to install a kernel module into UML.  The UML
kernel is built from linux 2.6.2, 32-bit i386.  The rootfs is
Debian-Squeeze-x86-root_fs.   I was able to build the kernel module
successful. But when I tried to insmod, I got the kernel panic.
After some debugging,  I found the kmalloc() during module init
returns NULL, and it was dereferenced later, hence the panic.

my question is:  is kmalloc() supported in UML (during kernel module
init)?  Is there anything special I need to do?

thanks
Han

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
Toralf Förster | 12 Mar 2013 21:59
Picon
Picon

[uml-user] WARNING: at mm/page_alloc.c:2386 __alloc_pages_nodemask+0x153/0x750()

While trying trinity under a UML I often run into this situation :

2013-03-12T21:54:41.934+01:00 trinity kernel: ------------[ cut here ]------------
2013-03-12T21:54:41.934+01:00 trinity kernel: WARNING: at mm/page_alloc.c:2386 __alloc_pages_nodemask+0x153/0x750()
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fcfc:  [<083426b8>] dump_stack+0x22/0x24
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd14:  [<0807d11a>] warn_slowpath_common+0x5a/0x80
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd3c:  [<0807d1e3>] warn_slowpath_null+0x23/0x30
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fd4c:  [<080d2bb3>] __alloc_pages_nodemask+0x153/0x750
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fdd8:  [<080d31d8>] __get_free_pages+0x28/0x50
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fdf0:  [<080fbe1f>] __kmalloc_track_caller+0x3f/0x180
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fe18:  [<080de616>] memdup_user+0x26/0x70
2013-03-12T21:54:41.934+01:00 trinity kernel: 3837fe34:  [<080de81e>] strndup_user+0x3e/0x60
2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fe50:  [<0823c493>] sys_request_key+0x53/0x170
2013-03-12T21:54:41.935+01:00 trinity kernel: 3837feac:  [<08062a92>] handle_syscall+0x82/0xb0
2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fef4:  [<08074e7d>] userspace+0x46d/0x590
2013-03-12T21:54:41.935+01:00 trinity kernel: 3837ffec:  [<0805f7cc>] fork_handler+0x6c/0x70
2013-03-12T21:54:41.935+01:00 trinity kernel: 3837fffc:  [<00000000>] 0x0
2013-03-12T21:54:41.935+01:00 trinity kernel:
2013-03-12T21:54:41.935+01:00 trinity kernel: ---[ end trace 2e631e8b4588be93 ]---
2013-03-12T21:54:41.935+01:00 trinity kernel: VFS: Warning: trinity-child0 using old stat() call.
Recompile your binary.
2013-03-12T21:54:41.935+01:00 trinity kernel: VFS: Warning: trinity-child0 using old stat() call.
Recompile your binary.

>From the author of trinity I was told:

	Looks like the "tried to kmalloc more than what kmalloc can do" bug.
	That shows up from time to time in various places.

	Not sure how this can happen from this trace, because it looks like
(Continue reading)


Gmane