From: Antonio Quartulli <ordex@autistici.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Sven Eckelmann <sven@narfation.org>,
b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
davem@davemloft.net, Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: Re: [B.A.T.M.A.N.] [PATCH] net: fix possible deadlocks in rtnl_trylock/unlock
Date: Mon, 3 Dec 2012 21:09:06 +0100 [thread overview]
Message-ID: <20121203200906.GJ27828@ritirata.org> (raw)
In-Reply-To: <20121201200153.GA1002@pandem0nium>
[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]
On Sat, Dec 01, 2012 at 09:01:53PM +0100, Simon Wunderlich wrote:
> On Sat, Dec 01, 2012 at 11:44:34AM -0800, Eric Dumazet wrote:
> > On Sat, 2012-12-01 at 20:04 +0100, Sven Eckelmann wrote:
> > > On Saturday 01 December 2012 10:36:12 Eric Dumazet wrote:
> > >
> > > > > diff --git a/net/bridge/br_sysfs_br.c b/net/bridge/br_sysfs_br.c
> > > > > index c5c0593..c122782 100644
> > > > > --- a/net/bridge/br_sysfs_br.c
> > > > > +++ b/net/bridge/br_sysfs_br.c
> > > > > @@ -142,7 +142,7 @@ static ssize_t store_stp_state(struct device *d,
> > > > >
> > > > > if (!rtnl_trylock())
> > > > >
> > > > > return restart_syscall();
> > > > >
> > > > > br_stp_set_enabled(br, val);
> > > > >
> > > > > - rtnl_unlock();
> > > > > + __rtnl_unlock();
> > > > >
> > > > > return len;
> > > > >
> > > > > }
> > > >
> > > > 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
> >
> > rtnl_trylock() could set a boolean flag to explicitly WARN_ON()
> > in case we try to unregister a device.
>
> Well, I'm not sure if this can happen in the bridge code, but from looking at the
> code it doesn't appear to be impossible. It would be better to be sure that it can't
> deadlock IMHO.
>
> (Although doing unlock/lock/unlock in an unlock function is also a little "uncommon").
But still we have the problem in batman-adv (as Sven pointed out in a previous
email) that tries to unregister a device in that "critical window".
Exporting __rtnl_unlock() would solve the issue in this case.
If you think the bridge code should not end up in such situation, what if Simon
resends the patch with only the __rtnl_unlock() exportation and the change in
batman-adv?
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-03 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 17:29 [PATCH] net: fix possible deadlocks in rtnl_trylock/unlock Simon Wunderlich
2012-12-01 18:07 ` [B.A.T.M.A.N.] " Sven Eckelmann
2012-12-01 18:36 ` Eric Dumazet
2012-12-01 19:04 ` Re: [B.A.T.M.A.N.] " Sven Eckelmann
2012-12-01 19:44 ` Eric Dumazet
2012-12-01 19:57 ` Sven Eckelmann
2012-12-01 20:01 ` Simon Wunderlich
2012-12-03 20:09 ` Antonio Quartulli [this message]
2012-12-03 20:50 ` Re: Re: [B.A.T.M.A.N.] " Sven Eckelmann
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=20121203200906.GJ27828@ritirata.org \
--to=ordex@autistici.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sven@narfation.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).