From: Nick Orlov <bugfixer@list.ru>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.34.4: BUG: sleeping function called from invalid context at mm/rmap.c:119
Date: Tue, 17 Aug 2010 20:38:02 -0400 [thread overview]
Message-ID: <20100818003802.GA3555@nickolas.homeunix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2481 bytes --]
All,
Starting with 2.6.34.4 I'm getting bunch of
Aug 15 19:00:01 xxx kernel: Freeing unused kernel memory: 1636k freed
Aug 15 19:00:01 xxx kernel: BUG: sleeping function called from invalid
context at mm/rmap.c:119
Aug 15 19:00:01 xxx kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1,
name: swapper
Aug 15 19:00:01 xxx kernel: 1 lock held by swapper/1:
Aug 15 19:00:01 xxx kernel: #0: (&p->cred_guard_mutex){+.+.+.}, at:
[<c10abf05>] prepare_bprm_creds+0x25/0x70
Aug 15 19:00:01 xxx kernel: Pid: 1, comm: swapper Not tainted
2.6.34.4-1.swp #1
Aug 15 19:00:01 xxx kernel: Call Trace:
Aug 15 19:00:01 xxx kernel: [<c12c7e84>] ? printk+0x18/0x1c
Aug 15 19:00:01 xxx kernel: [<c102a419>] __might_sleep+0x109/0x130
Aug 15 19:00:01 xxx kernel: [<c109a705>] anon_vma_prepare+0x25/0x130
Aug 15 19:00:01 xxx kernel: [<c105ad85>] ?
lock_release_holdtime+0xa5/0x1a0
Aug 15 19:00:01 xxx kernel: [<c1096228>] expand_downwards+0x18/0x180
Aug 15 19:00:01 xxx kernel: [<c1022f5c>] ? kmap_atomic_prot+0x7c/0xe0
Aug 15 19:00:01 xxx kernel: [<c1096398>] expand_stack+0x8/0x10
Aug 15 19:00:01 xxx kernel: [<c109303a>] handle_mm_fault+0x80a/0x840
Aug 15 19:00:01 xxx kernel: [<c109318a>] __get_user_pages+0x11a/0x370
Aug 15 19:00:01 xxx kernel: [<c109347f>] get_user_pages+0x4f/0x60
Aug 15 19:00:01 xxx kernel: [<c10ab71d>] get_arg_page+0x4d/0xa0
Aug 15 19:00:01 xxx kernel: [<c116fe76>] ? strnlen_user+0x26/0x50
Aug 15 19:00:01 xxx kernel: [<c10ab839>] copy_strings+0xc9/0x180
Aug 15 19:00:01 xxx kernel: [<c10ab914>] copy_strings_kernel+0x24/0x40
Aug 15 19:00:01 xxx kernel: [<c10ad2e2>] do_execve+0x182/0x250
Aug 15 19:00:01 xxx kernel: [<c1009c5d>] sys_execve+0x2d/0x60
Aug 15 19:00:01 xxx kernel: [<c1002bc6>] ptregs_execve+0x12/0x18
Aug 15 19:00:01 xxx kernel: [<c12cbc6d>] ? syscall_call+0x7/0xb
Aug 15 19:00:01 xxx kernel: [<c100694f>] ? kernel_execve+0x1f/0x30
Aug 15 19:00:01 xxx kernel: [<c10011b7>] ? run_init_process+0x17/0x20
Aug 15 19:00:01 xxx kernel: [<c100121a>] ? init_post+0x5a/0xc0
Aug 15 19:00:01 xxx kernel: [<c140f3d0>] ? kernel_init+0x1af/0x1b9
Aug 15 19:00:01 xxx kernel: [<c140f221>] ? kernel_init+0x0/0x1b9
Aug 15 19:00:01 xxx kernel: [<c100307a>] ?
kernel_thread_helper+0x6/0x1c
I'm actually surprised noone have reported it yet ....
Is it a known issue? Is there a patch I can try?
P.S. Any additional info is available by request.
P.P.S. I'm not subscribed to LKML, so please CC me.
Thank you,
Nick.
--
With best wishes,
Nick Orlov.
[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 14091 bytes --]
next reply other threads:[~2010-08-18 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 0:38 Nick Orlov [this message]
2010-08-20 2:00 ` Nick Orlov
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=20100818003802.GA3555@nickolas.homeunix.com \
--to=bugfixer@list.ru \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®