From: Jay Vosburgh <fubar@us.ibm.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Chuck Ebbert <cebbert@redhat.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: Bonding two 802.1q interfaces triggers "sleeping function called from invalid context"
Date: Tue, 01 May 2007 13:33:26 -0700 [thread overview]
Message-ID: <6380.1178051606@death> (raw)
In-Reply-To: <20070501193105.GA4737@gospo.rdu.redhat.com>
Andy Gospodarek <andy@greyhouse.net> wrote:
>> I need to use a bonding through two 802.1q tag VLAN virtual interface in the
>> same physical network interface. When I bond interface with command :
>> ifenslave bond0 eth1.10 eth1.20
>> Console and dmesg will continues report BUG:
>> --------------Output1 begin kernel 2.6.20-1.2933.fc6------------
>> BUG: sleeping function called from invalid context at include/asm/uaccess.h:500
>> in_atomic():1, irqs_disabled():0
>> [<c04ecadb>] copy_from_user+0x35/0x66
>> [<c05c2e78>] dev_ethtool+0x51/0xa0d
>> [<c05ee503>] tcp_current_mss+0x71/0xdf
>> [<c05ee169>] tcp_rcv_established+0x74f/0x7de
>> [<c04cf48f>] selinux_netlbl_sock_rcv_skb+0x1d/0x5b
>> [<c05f3a78>] tcp_v4_do_rcv+0x1bf/0x49c
>> [<c05f5f1b>] tcp_v4_rcv+0x564/0x8b1
>> [<d8a3ac03>] vlan_dev_ioctl+0x7b/0xa7 [8021q]
>> [<d8a3ab88>] vlan_dev_ioctl+0x0/0xa7 [8021q]
>> [<d8a53102>] bond_update_speed_duplex+0x88/0xd7 [bonding]
>> [<d8a5688e>] bond_mii_monitor+0x0/0x403 [bonding]
>> [<d8a56c01>] bond_mii_monitor+0x373/0x403 [bonding]
>
>Jay Vosburgh and I have been working on something to address this and
>other issues related to possible sleeping activities that might come
>from the monitoring functions. I feel like we are getting close to
>something so I hope we can post something soon.
>
>Care to add anything, Jay?
I was thinking about this one a couple of days ago; it's a
little tricky to get out of, since we nominally need to do the ethtool
calls holding only rtnl, but don't want to cycle rtnl for each monitor
pass.
The warning only shows up with VLANs because VLAN get_settings()
calls dev_ethtool() directly, and the copy_from_user() in dev_ethtool()
is the complaining party here.
Calling an end device driver's get_settings() directly doesn't
trigger the warning. I think that's safe without rtnl (at least insofar
as the slave won't vanish), since the slave cannot vanish without
bonding being notified via the NETDEV_UNREGISTER notifier.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2007-05-01 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:47 Bonding two 802.1q interfaces triggers "sleeping function called from invalid context" Chuck Ebbert
2007-05-01 19:31 ` Andy Gospodarek
2007-05-01 20:33 ` Jay Vosburgh [this message]
2007-05-01 22:06 ` Andy Gospodarek
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=6380.1178051606@death \
--to=fubar@us.ibm.com \
--cc=andy@greyhouse.net \
--cc=cebbert@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).