[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090802.130704.133993421.davem@davemloft.net>
Date: Sun, 02 Aug 2009 13:07:04 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: herbert@...dor.apana.org.au
Cc: mpm@...enic.com, netdev@...r.kernel.org, mcarlson@...adcom.com
Subject: Re: netpoll + xmit_lock == deadlock
From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Wed, 29 Jul 2009 15:35:23 +0800
> So if a driver is in the TX path, and a printk occurs, then a
> recursive dead lock can occur if that driver tries to take the
> xmit lock in its poll function to clean up descriptors.
My position has always been that such printk's are simply
not allowed. (check archives if you don't believe me :-)
The locking is going to get rediculious if we start having
to account for this.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists