From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>, Oleg Nesterov <oleg@redhat.com>
Subject: [GIT PULL] workqueue for v2.6.35-rc1
Date: Tue, 18 May 2010 18:32:54 +0200 [thread overview]
Message-ID: <4BF2C136.4020104@kernel.org> (raw)
Hello, Linus.
Please pull from the following branch to receive wq changes for
v2.6.35-rc1.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-linus
Bulk of cmwq still waiting for scheduler hooks to be resolved, there
are only two commits for v2.6.35-rc1.
One adds comment to flush_scheduled_work() mostly warning about the
possibility of deadlock. The other makes cancel_work_sync() clear
work->data which speeds up further cancel/flush requests on it and
also makes it safe to call cancel/flush on already canceled works even
if the previous workqueue is destroyed.
Thanks.
Alan Stern (1):
workqueue: warn about flush_scheduled_work()
Oleg Nesterov (1):
workqueue: change cancel_work_sync() to clear work->data
kernel/workqueue.c | 36 +++++++++++++++++++++++++++++++++++-
1 files changed, 35 insertions(+), 1 deletions(-)
--
tejun
reply other threads:[~2010-05-18 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BF2C136.4020104@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 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.