From: Jarek Poplawski <jarkao2@gmail.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jarek Poplawski <jarkao2@o2.pl>,
Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueues: lockdep annotations for flush_work()
Date: Sun, 6 Jul 2008 19:35:38 +0200 [thread overview]
Message-ID: <20080706173538.GA2500@ami.dom.local> (raw)
In-Reply-To: <20080706162800.GA6443@tv-sign.ru>
On Sun, Jul 06, 2008 at 08:28:00PM +0400, Oleg Nesterov wrote:
> Add lockdep annotations to flush_work() and update the comment.
>
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Looks OK to me. (But probably the comment on "true" would be easier
(more precise).)
Regards,
Jarek P.
>
> --- 26-rc2/kernel/workqueue.c~FW_LOCKDEP 2008-06-29 19:36:27.000000000 +0400
> +++ 26-rc2/kernel/workqueue.c 2008-07-06 20:15:16.000000000 +0400
> @@ -403,6 +403,8 @@ EXPORT_SYMBOL_GPL(flush_workqueue);
> * flush_work - block until a work_struct's callback has terminated
> * @work: the work which is to be flushed
> *
> + * Returns false if @work has already terminated.
> + *
> * It is expected that, prior to calling flush_work(), the caller has
> * arranged for the work to not be requeued, otherwise it doesn't make
> * sense to use this function.
> @@ -418,6 +420,9 @@ int flush_work(struct work_struct *work)
> if (!cwq)
> return 0;
>
> + lock_acquire(&cwq->wq->lockdep_map, 0, 0, 0, 2, _THIS_IP_);
> + lock_release(&cwq->wq->lockdep_map, 1, _THIS_IP_);
> +
> prev = NULL;
> spin_lock_irq(&cwq->lock);
> if (!list_empty(&work->entry)) {
>
prev parent reply other threads:[~2008-07-06 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 16:28 Oleg Nesterov
2008-07-06 17:35 ` Jarek Poplawski [this message]
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=20080706173538.GA2500@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jarkao2@o2.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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
Powered by JetHome