From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: called althought it is marked as AVOID.
Date: Mon, 22 Apr 2013 15:53:48 -0400 [thread overview]
Message-ID: <20130422195348.GA12899@redhat.com> (raw)
In-Reply-To: <5172F41A.7060704@gmx.de>
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
prev parent reply other threads:[~2013-04-22 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 20:01 called althought it is marked as AVOID Toralf Förster
2013-04-22 19:53 ` Dave Jones [this message]
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=20130422195348.GA12899@redhat.com \
--to=davej@redhat.com \
--cc=toralf.foerster@gmx.de \
--cc=trinity@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).