From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-mm@kvack.org, user-mode-linux-user@lists.sourceforge.net,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: SLAB + UML : WARNING: at mm/page_alloc.c:2386
Date: Thu, 14 Mar 2013 20:53:05 +0100 [thread overview]
Message-ID: <CAFLxGvxeOyg=zXqK+q5BpTHcpnaymk0_cyTUkUyRxD_C3czZww@mail.gmail.com> (raw)
In-Reply-To: <51422008.3020208@gmx.de>
On Thu, Mar 14, 2013 at 8:07 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
> The following WARNING: can be triggered sometimes with trinity [1] under a user mode linux image
> using the SLUB allocator (and not with SLAB)
>
>
> 2013-03-14T19:09:51.071+01:00 trinity kernel: ------------[ cut here ]------------
> 2013-03-14T19:09:51.071+01:00 trinity kernel: WARNING: at mm/page_alloc.c:2386 __alloc_pages_nodemask+0x153/0x750()
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fd14: [<08342dd8>] dump_stack+0x22/0x24
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fd2c: [<0807d0da>] warn_slowpath_common+0x5a/0x80
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fd54: [<0807d1a3>] warn_slowpath_null+0x23/0x30
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fd64: [<080d3213>] __alloc_pages_nodemask+0x153/0x750
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fdf0: [<080d3838>] __get_free_pages+0x28/0x50
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fe08: [<080fc48f>] __kmalloc_track_caller+0x3f/0x180
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fe30: [<080dec76>] memdup_user+0x26/0x70
> 2013-03-14T19:09:51.071+01:00 trinity kernel: 3899fe4c: [<080dee7e>] strndup_user+0x3e/0x60
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899fe68: [<0811b440>] copy_mount_string+0x30/0x50
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899fe7c: [<0811be0a>] sys_mount+0x1a/0xe0
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899feac: [<08062a92>] handle_syscall+0x82/0xb0
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899fef4: [<08074e7d>] userspace+0x46d/0x590
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899ffec: [<0805f7cc>] fork_handler+0x6c/0x70
> 2013-03-14T19:09:51.076+01:00 trinity kernel: 3899fffc: [<5a5a5a5a>] 0x5a5a5a5a
> 2013-03-14T19:09:51.076+01:00 trinity kernel:
> 2013-03-14T19:09:51.076+01:00 trinity kernel: ---[ end trace fd6f346f805efdbe ]---
Looks like strndup_user() triggers the issue.
In another trace also strndup_user() appeared.
--
Thanks,
//richard
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-03-14 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 19:07 Toralf Förster
2013-03-14 19:53 ` richard -rw- weinberger [this message]
2013-03-14 20:51 ` richard -rw- weinberger
2013-03-14 20:58 ` SLUB " Toralf Förster
2013-03-14 21:21 ` Dave Jones
2013-03-14 21:24 ` Toralf Förster
2013-03-14 23:10 ` richard -rw- weinberger
2013-03-15 18:44 ` Toralf Förster
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='CAFLxGvxeOyg=zXqK+q5BpTHcpnaymk0_cyTUkUyRxD_C3czZww@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=toralf.foerster@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox