[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1261060259.10356.112.camel@johannes.local>
Date: Thu, 17 Dec 2009 15:30:59 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Jarek Poplawski <jarkao2@...il.com>
Cc: Mikhail Markine <markine@...gle.com>,
Jay Vosburgh <fubar@...ibm.com>,
David Miller <davem@...emloft.net>,
bonding-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
Petri Gynther <pgynther@...gle.com>
Subject: Re: [PATCH] bonding: cancel_delayed_work() ->
cancel_delayed_work_sync()
On Thu, 2009-12-17 at 13:36 +0000, Jarek Poplawski wrote:
> On Thu, Dec 17, 2009 at 02:19:46PM +0100, Johannes Berg wrote:
> > Jarek,
> >
> > Sorry to mail you directly, but I only saw your reply on gmane and
> > didn't want to break up the threading etc.
> >
> > cancel_delayed_work_sync() should be ok in this case unless the work
> > items themselves used the rtnl,
>
> Hmm, I'm not sure I get your point, but e.g. bond_mii_monitor() work
> function can get rtnl_lock().
Ok in that case you can't cancel_sync() it under rtnl. I was thinking of
the case where it's just not ok because of other work. Sorry for the
confusion!
johannes
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists