[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8364190.7CxpSxJp4n@sven-laptop.home.narfation.org>
Date: Sat, 01 Dec 2012 20:57:51 +0100
From: Sven Eckelmann <sven@...fation.org>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: b.a.t.m.a.n@...ts.open-mesh.org,
Simon Wunderlich <simon.wunderlich@...03.tu-chemnitz.de>,
netdev@...r.kernel.org, davem@...emloft.net,
Simon Wunderlich <siwu@....tu-chemnitz.de>
Subject: Re: Re: Re: [B.A.T.M.A.N.] [PATCH] net: fix possible deadlocks in rtnl_trylock/unlock
On Saturday 01 December 2012 11:44:34 Eric Dumazet wrote:
[...]
> > > 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
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists