Thread (9 messages) 9 messages, 5 authors, 2012-12-03

Re: [PATCH] net: fix possible deadlocks in rtnl_trylock/unlock

From: Sven Eckelmann <hidden>
Date: 2012-12-01 19:57:51
Also in: batman

On Saturday 01 December 2012 11:44:34 Eric Dumazet wrote:
[...]
quoted
quoted
I have no idea of why you believe there is a problem here.

Could you explain how net_todo_list could be not empty ?

As long as no device is unregistered between
rtnl_trylock()/rtnl_unlock(), there is no possible deadlock.
I am not sure what "here" means for your. At least batman-adv tries to
unregister a device -> problem [1]. I will not make any judgements about
the other uses in the kernel/other parts patched by Simon.
I was reacting to the change in net/bridge/br_sysfs_br.c
Yes, in this context it makes more sense.
rtnl_trylock() could set a boolean flag to explicitly WARN_ON()
in case we try to unregister a device.
Sounds interesting.

Kind regards,
	Sven

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help