netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org,
	Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: Re: sleeping function called from invalid context (rtnetlink)
Date: Thu, 1 Mar 2012 16:53:32 -0800	[thread overview]
Message-ID: <CAL4WiirCK6a5pgHCZyL7WAC6xrOnBWnx+6tw73x0StWfoPdaHw@mail.gmail.com> (raw)
In-Reply-To: <20120301235928.GA28088@redhat.com>

Le 1 mars 2012 15:59, Dave Jones <davej@redhat.com> a écrit :
> Just had this reported by a Fedora user.
> It's against 3.3-rc4, but afaik, the only changes to rtnetlink
> since then wouldn't have fixed this unless I've overlooked something.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=799099
>
> BUG: sleeping function called from invalid context at kernel/mutex.c:271
> in_atomic(): 1, irqs_disabled(): 0, pid: 10451, name: NetworkManager
> INFO: lockdep is turned off.
> Pid: 10451, comm: NetworkManager Not tainted 3.3.0-0.rc4.git1.4.fc17.x86_64 #1
> Call Trace:
>  [<ffffffff810966fc>] __might_sleep+0x13c/0x200
>  [<ffffffff8154c470>] ? sock_def_readable+0x30/0x1c0
>  [<ffffffff8169a81e>] mutex_lock_nested+0x2e/0x3a0
>  [<ffffffff81571100>] ? rtnetlink_net_init+0x50/0x50
>  [<ffffffff8158e25c>] ? netlink_dump_start+0xdc/0x180
>  [<ffffffff81571100>] ? rtnetlink_net_init+0x50/0x50
>  [<ffffffff81571897>] rtnl_lock+0x17/0x20
>  [<ffffffff81573ef8>] rtnetlink_rcv_msg+0x1f8/0x2e0
>  [<ffffffff81571897>] ? rtnl_lock+0x17/0x20
>  [<ffffffff81573d00>] ? __rtnl_unlock+0x20/0x20
>  [<ffffffff815901b1>] netlink_rcv_skb+0xa1/0xb0
>  [<ffffffff815718c5>] rtnetlink_rcv+0x25/0x40
>  [<ffffffff8158fafd>] netlink_unicast+0x19d/0x1f0
>  [<ffffffff8158fe2b>] netlink_sendmsg+0x2db/0x360
>  [<ffffffff8154c66d>] ? sock_update_netprioidx+0x6d/0x250
>  [<ffffffff81544888>] sock_sendmsg+0xf8/0x130
>  [<ffffffff81545f9d>] ? sock_recvmsg+0xfd/0x130
>  [<ffffffff811745d5>] ? might_fault+0xa5/0xb0
>  [<ffffffff8117458c>] ? might_fault+0x5c/0xb0
>  [<ffffffff81555266>] ? verify_iovec+0x56/0xd0
>  [<ffffffff81545e8e>] __sys_sendmsg+0x42e/0x440
>  [<ffffffff811bd612>] ? fget_light+0x62/0x4a0
>  [<ffffffff811bd6a0>] ? fget_light+0xf0/0x4a0
>  [<ffffffff811bd612>] ? fget_light+0x62/0x4a0
>  [<ffffffff81548c59>] sys_sendmsg+0x49/0x90
>  [<ffffffff816a74a9>] system_call_fastpath+0x16/0x1b
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Yes, this is on my TODO list, it should be done in a couple of days.

Thanks

  reply	other threads:[~2012-03-02  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-799099-176318@bugzilla.redhat.com>
2012-03-01 23:59 ` sleeping function called from invalid context (rtnetlink) Dave Jones
2012-03-02  0:53   ` Eric Dumazet [this message]
2012-03-04  5:00   ` Eric Dumazet
2012-03-04  5:47     ` David Miller

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=CAL4WiirCK6a5pgHCZyL7WAC6xrOnBWnx+6tw73x0StWfoPdaHw@mail.gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=davej@redhat.com \
    --cc=kernel-team@fedoraproject.org \
    --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).