From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Crashes in 3.14.13+ related to anon_vma_clone.
Date: Thu, 24 Jul 2014 16:08:17 -0700 [thread overview]
Message-ID: <53D191E1.3080107@candelatech.com> (raw)
A few of our systems are repeatedly crashing when upgraded from
the 3.14.6+ to 3.14.13+ kernels. Both kernels have a fair bit
of our out-of-tree patches, so could be our fault.
But, in case this is a known problem...has anyone seen crashes like
this below?
Test case is using some ath9k APs and stations, but not certain
that has much to do with the problem.
BUG: unable to handle kernel paging request at 0000003f9840b000
IP: [<ffffffff81169ae8>] anon_vma_clone+0x88/0xf5
PGD be580067 PUD bab85067 PMD babd5067 PTE 80000000bebbd065
Oops: 0003 [#1] PREEMPT SMP
Modules linked in: 8021q garp stp mrp llc fuse macvlan wanlink(O) pktgen ip6table_filter ip6_tables ebtable_nat ebtables coretemp hwmoo
CPU: 1 PID: 1777 Comm: btserver Tainted: G C O 3.14.13+ #19
Hardware name: To be filled by O.E.M. To be filled by O.E.M./To be filled by O.E.M., BIOS 4.6.3 03/06/2012
task: ffff88020dcfb100 ti: ffff8800baa3e000 task.ti: ffff8800baa3e000
RIP: 0010:[<ffffffff81169ae8>] [<ffffffff81169ae8>] anon_vma_clone+0x88/0xf5
RSP: 0018:ffff8800baa3fda0 EFLAGS: 00010246
RAX: ffff8800ba8b8380 RBX: 0000003f9840b000 RCX: 000000000142b101
RDX: 0000000000000000 RSI: ffff8800ba8b8380 RDI: ffff8800ba8b8388
RBP: ffff8800baa3fdd0 R08: 0000000000015d60 R09: 0000003f9840b000
R10: 000000000000000b R11: 0000000000016338 R12: 0000000000000000
R13: ffff8800bc609450 R14: ffff8802212db980 R15: ffff8800ba8b8380
FS: 00007f0b70511740(0000) GS:ffff88022bc80000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000003f9840b000 CR3: 00000000bab8f000 CR4: 00000000000007e0
Stack:
ffff880221ba92a0 ffff88020dcfc980 ffff8800bc609450 ffff880221ba9228
ffff8800bc609450 ffff880221ba9228 ffff8800baa3fe08 ffffffff81169b7b
ffff88020dcfc980 ffff880211db5f80 ffff880221ba9228 ffff8800bc609450
Call Trace:
[<ffffffff81169b7b>] anon_vma_fork+0x26/0xec
[<ffffffff810c0070>] copy_process.part.28+0xf98/0x16ca
[<ffffffff810c091d>] do_fork+0xb4/0x211
[<ffffffff810cbe9b>] ? __set_task_blocked+0x5e/0x64
[<ffffffff815a1b9f>] ? _raw_spin_unlock_irq+0xc/0x1f
[<ffffffff810c0ae0>] SyS_clone+0x11/0x13
[<ffffffff815a6a59>] stub_clone+0x69/0x90
[<ffffffff815a66fd>] ? system_call_fastpath+0x1a/0x1f
Code: 48 8b 3d 64 f1 b0 00 be d0 00 00 00 e8 9b 5e 01 00 48 85 c0 48 89 c3 74 62 45 31 e4 4d 8b 7e 08 4c 89 e7 49 8b 37 e8 fa ec ff ff
RIP [<ffffffff81169ae8>] anon_vma_clone+0x88/0xf5
RSP <ffff8800baa3fda0>
CR2: 0000003f9840b000
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2014-07-24 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 23:08 Ben Greear [this message]
2014-07-24 23:38 ` Ben Greear
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=53D191E1.3080107@candelatech.com \
--to=greearb@candelatech.com \
--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
Powered by JetHome