From: Dave Jones <davej@redhat.com>
To: netdev@vger.kernel.org
Subject: kmalloc with locks held in xfrm.
Date: Thu, 27 Feb 2014 10:19:54 -0500 [thread overview]
Message-ID: <20140227151954.GA30946@redhat.com> (raw)
Hit this trace this morning on rc4.
Dave
BUG: sleeping function called from invalid context at mm/slub.c:965
in_atomic(): 0, irqs_disabled(): 0, pid: 28692, name: trinity-main
2 locks held by trinity-main/28692:
#0: (sk_lock-AF_INET){......}, at: [<ffffffff83660cd3>] do_ip_setsockopt.isra.12+0x63/0xe10
#1: (rcu_read_lock){......}, at: [<ffffffff836bf138>] xfrm_user_policy+0xa8/0x1c0
CPU: 0 PID: 28692 Comm: trinity-main Not tainted 3.14.0-rc4+ #125
ffffffff83a428e7 00000000707766bf ffff88008c749c50 ffffffff8372e248
ffff8800075c45c0 ffff88008c749c80 ffffffff8309c525 00000000000000d0
00000000000000d0 0000000000000008 ffff880244c04240 ffff88008c749cd8
Call Trace:
[<ffffffff8372e248>] dump_stack+0x4e/0x7a
[<ffffffff8309c525>] __might_sleep+0x125/0x180
[<ffffffff831acd6a>] __kmalloc+0x7a/0x2a0
[<ffffffffc05978d8>] ? pfkey_compile_policy+0x1a8/0x270 [af_key]
[<ffffffffc05978d8>] pfkey_compile_policy+0x1a8/0x270 [af_key]
[<ffffffff836bf1b7>] xfrm_user_policy+0x127/0x1c0
[<ffffffff836bf138>] ? xfrm_user_policy+0xa8/0x1c0
[<ffffffff83071907>] ? __local_bh_enable_ip+0x67/0xe0
[<ffffffff8366173e>] do_ip_setsockopt.isra.12+0xace/0xe10
[<ffffffff831c1e7c>] ? get_empty_filp+0x5c/0x240
[<ffffffff830bcab5>] ? cpuacct_account_field+0x5/0xc0
[<ffffffff8310ff8e>] ? __acct_update_integrals+0x8e/0x120
[<ffffffff830a388d>] ? get_parent_ip+0xd/0x50
[<ffffffff8373d42b>] ? preempt_count_sub+0x6b/0xf0
[<ffffffff83661ab0>] ip_setsockopt+0x30/0xa0
[<ffffffff836872eb>] udp_setsockopt+0x1b/0x40
[<ffffffff83600dc4>] sock_common_setsockopt+0x14/0x20
[<ffffffff835ffa30>] SyS_setsockopt+0x80/0xf0
[<ffffffff83741e6a>] tracesys+0xd4/0xd9
next reply other threads:[~2014-02-27 15:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 15:19 Dave Jones [this message]
2014-02-27 16:17 ` Possible fix Nikolay Aleksandrov
2014-02-27 16:24 ` Nikolay Aleksandrov
2014-02-27 17:05 ` Nikolay Aleksandrov
2014-02-28 7:23 ` Steffen Klassert
2014-02-28 10:10 ` Nikolay Aleksandrov
2014-02-28 22:10 ` Paul Moore
2014-03-02 16:26 ` Nikolay Aleksandrov
2014-03-05 12:20 ` Steffen Klassert
2014-03-07 3:04 ` Paul Moore
2014-03-07 11:23 ` Steffen Klassert
2014-03-07 15:50 ` Paul Moore
2014-03-04 12:26 ` [PATCH 0/2] af_key: fixes for sleeping while atomic Nikolay Aleksandrov
2014-03-04 12:26 ` [PATCH 1/2] net: af_key: fix sleeping under rcu Nikolay Aleksandrov
2014-03-04 12:46 ` David Laight
2014-03-04 21:40 ` David Miller
2014-03-04 12:26 ` [PATCH 2/2] selinux: add gfp argument to security_xfrm_policy_alloc and fix callers Nikolay Aleksandrov
2014-03-07 3:22 ` Paul Moore
2014-03-07 10:52 ` Nikolay Aleksandrov
2014-03-05 12:07 ` [PATCH 0/2] af_key: fixes for sleeping while atomic Steffen Klassert
2014-03-05 22:21 ` Paul Moore
2014-03-07 11:44 ` [PATCHv2 " Nikolay Aleksandrov
2014-03-07 11:44 ` [PATCHv2 1/2] net: af_key: fix sleeping under rcu Nikolay Aleksandrov
2014-03-07 11:44 ` [PATCHv2 2/2] selinux: add gfp argument to security_xfrm_policy_alloc and fix callers Nikolay Aleksandrov
2014-03-07 22:27 ` Paul Moore
2014-03-10 12:52 ` Steffen Klassert
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=20140227151954.GA30946@redhat.com \
--to=davej@redhat.com \
--cc=netdev@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).