* called althought it is marked as AVOID.
@ 2013-04-20 20:01 Toralf Förster
2013-04-22 19:53 ` Dave Jones
0 siblings, 1 reply; 2+ messages in thread
From: Toralf Förster @ 2013-04-20 20:01 UTC (permalink / raw)
To: trinity
Running trinity within a user mode linux image yield into :
2013-04-20T21:48:16.000+02:00 trinity tfoerste: W=/mnt/nfs/n22/w
2013-04-20T21:48:21.926+02:00 trinity kernel: ------------[ cut here ]------------
2013-04-20T21:48:21.926+02:00 trinity kernel: WARNING: at mm/mmap.c:2702 exit_mmap+0x161/0x170()
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bd90: [<0836fe08>] dump_stack+0x22/0x24
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bda8: [<0807f1da>] warn_slowpath_common+0x5a/0x80
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bdd0: [<0807f2a3>] warn_slowpath_null+0x23/0x30
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bde0: [<080e9231>] exit_mmap+0x161/0x170
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be18: [<0807cdd9>] mmput+0x39/0x90
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be2c: [<08083f00>] do_exit+0x2d0/0x820
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be7c: [<08084527>] do_group_exit+0x97/0xe0
2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bea0: [<08084589>] sys_exit_group+0x19/0x20
2013-04-20T21:48:21.930+02:00 trinity kernel: 1844beac: [<08064a92>] handle_syscall+0x82/0xb0
2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bef4: [<08076f2d>] userspace+0x46d/0x590
2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bfec: [<080617fc>] fork_handler+0x6c/0x70
2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bffc: [<00000000>] 0x0
2013-04-20T21:48:21.930+02:00 trinity kernel:
2013-04-20T21:48:21.930+02:00 trinity kernel: ---[ end trace 9f502214d4921e53 ]---
The trinity command line was :
$> trinity.sh -x mremap -x mount -x add_key -x request_key -x keyctl -x clock_nanosleep
I'm wondering what does AVOID took to be ignored ?
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: called althought it is marked as AVOID.
2013-04-20 20:01 called althought it is marked as AVOID Toralf Förster
@ 2013-04-22 19:53 ` Dave Jones
0 siblings, 0 replies; 2+ messages in thread
From: Dave Jones @ 2013-04-22 19:53 UTC (permalink / raw)
To: Toralf Förster; +Cc: trinity
On Sat, Apr 20, 2013 at 10:01:30PM +0200, Toralf Förster wrote:
> Running trinity within a user mode linux image yield into :
>
>
> 2013-04-20T21:48:16.000+02:00 trinity tfoerste: W=/mnt/nfs/n22/w
> 2013-04-20T21:48:21.926+02:00 trinity kernel: ------------[ cut here ]------------
> 2013-04-20T21:48:21.926+02:00 trinity kernel: WARNING: at mm/mmap.c:2702 exit_mmap+0x161/0x170()
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bd90: [<0836fe08>] dump_stack+0x22/0x24
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bda8: [<0807f1da>] warn_slowpath_common+0x5a/0x80
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bdd0: [<0807f2a3>] warn_slowpath_null+0x23/0x30
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bde0: [<080e9231>] exit_mmap+0x161/0x170
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be18: [<0807cdd9>] mmput+0x39/0x90
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be2c: [<08083f00>] do_exit+0x2d0/0x820
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844be7c: [<08084527>] do_group_exit+0x97/0xe0
> 2013-04-20T21:48:21.926+02:00 trinity kernel: 1844bea0: [<08084589>] sys_exit_group+0x19/0x20
> 2013-04-20T21:48:21.930+02:00 trinity kernel: 1844beac: [<08064a92>] handle_syscall+0x82/0xb0
> 2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bef4: [<08076f2d>] userspace+0x46d/0x590
> 2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bfec: [<080617fc>] fork_handler+0x6c/0x70
> 2013-04-20T21:48:21.930+02:00 trinity kernel: 1844bffc: [<00000000>] 0x0
> 2013-04-20T21:48:21.930+02:00 trinity kernel:
> 2013-04-20T21:48:21.930+02:00 trinity kernel: ---[ end trace 9f502214d4921e53 ]---
>
>
> The trinity command line was :
>
> $> trinity.sh -x mremap -x mount -x add_key -x request_key -x keyctl -x clock_nanosleep
>
> I'm wondering what does AVOID took to be ignored ?
That trace is a process exiting, not a syscall being called.
Looks like something in uml leaked page table entries.
Dave
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-22 19:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-20 20:01 called althought it is marked as AVOID Toralf Förster
2013-04-22 19:53 ` Dave Jones
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).