Joonwoo Park <[EMAIL PROTECTED]> wrote: > Hi, > dev_set_rx_mode calls __dev_set_rx_mode with softirq disabled (by > netif_tx_lock_bh) > therefore __dev_set_promiscuity can be called with softirq disabled. > It will cause in_interrupt() to return true and ASSERT_RTNL warning. > Is there a good solution to fix it besides blowing ASSERT_RTNL up?
We've talked this one before on netdev. It's on my todo list to fix. The correct solution is to untangle this so that __dev_set_promiscuity does not get called in the first place on BH paths. Unfortunately I've been busy so I haven't completed the patches yet. But as this problem is not urgent let's not just put on a bandaid. Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
