All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Mikhail Markine <markine@google.com>,
	Jay Vosburgh <fubar@us.ibm.com>,
	David Miller <davem@davemloft.net>,
	bonding-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	Petri Gynther <pgynther@google.com>
Subject: Re: [PATCH] bonding: cancel_delayed_work() -> cancel_delayed_work_sync()
Date: Thu, 17 Dec 2009 13:36:44 +0000	[thread overview]
Message-ID: <20091217133644.GD8654@ff.dom.local> (raw)
In-Reply-To: <20091217074930.GA6779@ff.dom.local>


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().

> the common problem only happens with
> flush_scheduled_work() -- sync() is fine since either it's running, then
> you need the sync, or if it's not running it doesn't matter if something
> else is on the queue before it that's blocked on the rtnl.
> 
> If you could reply to the thread to that effect I'd appreciate it :)

No problem with this question :-)
Jarek P.

  reply	other threads:[~2009-12-17 13:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  0:28 [PATCH] bonding: cancel_delayed_work() -> cancel_delayed_work_sync() Mikhail Markine
2009-12-17  7:49 ` Jarek Poplawski
2009-12-17 13:36   ` Jarek Poplawski [this message]
2009-12-17 14:30     ` Johannes Berg
2009-12-17 16:12       ` [Bonding-devel] " Jay Vosburgh
2009-12-17 18:40         ` Jarek Poplawski
2009-12-17 18:49           ` Laurent Chavey
2009-12-17 19:37             ` Jay Vosburgh
2009-12-17 20:56               ` Jarek Poplawski
2009-12-17 21:16                 ` Jarek Poplawski
2009-12-17 21:40                 ` Jay Vosburgh
2009-12-17 21:58                   ` Jarek Poplawski
2009-12-17 22:33                     ` Jarek Poplawski
2009-12-17 21:25               ` Laurent Chavey
2009-12-17 21:31         ` Mikhail Markine

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=20091217133644.GD8654@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=johannes@sipsolutions.net \
    --cc=markine@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pgynther@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.