From: "Toralf Förster" <toralf.foerster@gmx.de>
To: user-mode-linux-user@lists.sourceforge.net
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: user mode linux: trinity syscall "madvise" triggers quickly BUG: Bad page map
Date: Thu, 04 Apr 2013 19:04:38 +0200 [thread overview]
Message-ID: <515DB2A6.7020902@gmx.de> (raw)
if SLUB is used (SLAB works fine till now with this syscall).
What I get with the this trinity command line
$> trinity --children 2 -c madvise
for a 32 bit Gentoo Linux (both as host and as guest)
and host kernel 3.8.5 and guest kernel 3.9-rc5 is the following :
2013-04-04T19:00:29.220+02:00 trinity kernel: BUG: Bad page map in process trinity-child1 pte:0032d045 pmd:3932e1e1
2013-04-04T19:00:29.220+02:00 trinity kernel: page:0a73f5a0 count:1 mapcount:-1 mapping: (null) index:0x0
2013-04-04T19:00:29.220+02:00 trinity kernel: page flags: 0x404(referenced|reserved)
2013-04-04T19:00:29.220+02:00 trinity kernel: addr:00100000 vm_flags:00040055 anon_vma: (null) mapping: (null) index:100
2013-04-04T19:00:29.220+02:00 trinity kernel: vma->vm_ops->fault: special_mapping_fault+0x0/0x80
2013-04-04T19:00:29.220+02:00 trinity kernel: 413c7d20: [<0836efd8>] dump_stack+0x22/0x24
2013-04-04T19:00:29.220+02:00 trinity kernel: 413c7d38: [<0837039b>] print_bad_pte+0x17b/0x197
2013-04-04T19:00:29.220+02:00 trinity kernel: 413c7d7c: [<080e2c68>] unmap_single_vma+0x268/0x430
2013-04-04T19:00:29.220+02:00 trinity kernel: 413c7ddc: [<080e33f4>] zap_page_range+0x74/0xb0
2013-04-04T19:00:29.220+02:00 trinity kernel: 413c7e10: [<080e172d>] sys_madvise+0x3bd/0x720
2013-04-04T19:00:29.225+02:00 trinity kernel: 413c7eac: [<08064a92>] handle_syscall+0x82/0xb0
2013-04-04T19:00:29.225+02:00 trinity kernel: 413c7ef4: [<08076f0d>] userspace+0x46d/0x590
2013-04-04T19:00:29.225+02:00 trinity kernel: 413c7fec: [<080617cc>] fork_handler+0x6c/0x70
2013-04-04T19:00:29.225+02:00 trinity kernel: 413c7ffc: [<00000002>] 0x2
2013-04-04T19:00:29.225+02:00 trinity kernel:
2013-04-04T19:00:29.225+02:00 trinity kernel: Disabling lock debugging due to kernel taint
2013-04-04T19:00:29.225+02:00 trinity kernel: BUG: Bad page state in process trinity-child1 pfn:0032d
2013-04-04T19:00:29.225+02:00 trinity kernel: page:0a73f5a0 count:0 mapcount:-1 mapping: (null) index:0x0
2013-04-04T19:00:29.225+02:00 trinity kernel: page flags: 0x404(referenced|reserved)
2013-04-04T19:00:29.225+02:00 trinity kernel: 413c7cd8: [<0836efd8>] dump_stack+0x22/0x24
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7cf0: [<080cf185>] bad_page+0xb5/0xe0
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d0c: [<080cf223>] free_pages_prepare+0x73/0xb0
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d28: [<080d064d>] free_hot_cold_page+0x1d/0x100
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d50: [<080d2fde>] __put_single_page+0x1e/0x30
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d64: [<080d3107>] put_page+0x27/0x30
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d6c: [<080f026c>] free_page_and_swap_cache+0x3c/0x50
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7d7c: [<080e2c85>] unmap_single_vma+0x285/0x430
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7ddc: [<080e33f4>] zap_page_range+0x74/0xb0
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7e10: [<080e172d>] sys_madvise+0x3bd/0x720
2013-04-04T19:00:29.230+02:00 trinity kernel: 413c7eac: [<08064a92>] handle_syscall+0x82/0xb0
2013-04-04T19:00:29.234+02:00 trinity kernel: 413c7ef4: [<08076f0d>] userspace+0x46d/0x590
2013-04-04T19:00:29.234+02:00 trinity kernel: 413c7fec: [<080617cc>] fork_handler+0x6c/0x70
2013-04-04T19:00:29.234+02:00 trinity kernel: 413c7ffc: [<00000002>] 0x2
2013-04-04T19:00:29.234+02:00 trinity kernel:
2013-04-04T19:00:30.174+02:00 trinity kernel: BUG: Bad rss-counter state mm:40623600 idx:0 val:-1
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next reply other threads:[~2013-04-04 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 17:04 Toralf Förster [this message]
[not found] ` <CAFLxGvyDxdL9BJHFH5O6OSqZ3ZyBatBvmZGJWP3B=D=0xcgVng@mail.gmail.com>
2013-04-06 12:47 ` user mode linux: trinity syscall "madvise" triggers quickly BUG: Bad page map Toralf Förster
2013-04-06 12:55 ` Toralf Förster
2013-04-06 16:45 ` richard -rw- weinberger
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=515DB2A6.7020902@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.