From: Oleg Nesterov <oleg@tv-sign.ru>
To: Daniel Drake <dsd@gentoo.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 3/6] workqueue: make cancel_rearming_delayed_workqueue() work on idle dwork
Date: Wed, 7 Feb 2007 18:16:30 +0300 [thread overview]
Message-ID: <20070207151630.GA138@tv-sign.ru> (raw)
In-Reply-To: <45C9E320.3070001@gentoo.org>
On 02/07, Daniel Drake wrote:
>
> Oleg Nesterov wrote:
> >cancel_rearming_delayed_workqueue(dwork) will hang forever if dwork was not
> >scheduled, because in that case cancel_delayed_work()->del_timer_sync()
> >never
> >returns true.
>
> Thanks! We hit this problem before with the zd1211rw driver and avoided
> using cancel_rearming_delayed_workqueue() for this reason.
Great. But I am afraid my changelog was incomplete. This patch only fixes
the cancel_rearming_delayed_workqueue(freshly_initialized_dwork) lockup.
The following code
schedule_delayed_work(dw);
cancel_rearming_delayed_workqueue(dw); // OK
cancel_rearming_delayed_workqueue(dw); // HANGS!
still doesn't work.
Is it worth fixing? The fix is very simple, and probably makes sense by
itself:
cancel_delayed_work:
- work_release(&work->work);
+ work->work.data = NULL;
Oleg.
next prev parent reply other threads:[~2007-02-07 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 23:30 [PATCH 3/6] workqueue: make cancel_rearming_delayed_workqueue() work on idle dwork Oleg Nesterov
2007-02-07 14:33 ` Daniel Drake
2007-02-07 15:16 ` Oleg Nesterov [this message]
2007-02-07 17:43 ` Oleg Nesterov
2007-02-08 2:20 ` Horms
2007-02-08 8:35 ` Oleg Nesterov
2007-02-08 8:39 ` Andrew Morton
2007-02-08 9:46 ` Oleg Nesterov
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=20070207151630.GA138@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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