From: Andy Walls <awalls@md.metrocast.net>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, nicolas.mailhot@laposte.net,
Jarod Wilson <jarod@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [V2 PATCH] kthread_work: Make lockdep happy
Date: Tue, 21 Dec 2010 19:39:53 -0500 [thread overview]
Message-ID: <1292978393.2401.14.camel@morgan.silverblock.net> (raw)
In-Reply-To: <20101221044050.GA25718@windriver.com>
On Tue, 2010-12-21 at 12:40 +0800, Yong Zhang wrote:
> From: Yong Zhang <yong.zhang0@gmail.com>
> Subject: [V2 PATCH] kthread_work: Make lockdep happy
>
> spinlock in kthread_worker and wait_queue_head in kthread_work
> both should be lockdep sensible.
> So change the interface to make it suiltable for CONFIG_LOCKDEP.
>
> Reported-by: Nicolas <nicolas.mailhot@laposte.net>
> Signed-off-by: Yong Zhang <yong.zhang0@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Andy Walls <awalls@md.metrocast.net>
> ---
> Changes from V1:
> *According to Tejun, kthread_worker could be defined on stack,
> So introduce DEFINE_KTHREAD_WORKER_ONSTACK.
> *Change wrong setting to kthread_work->task. Thanks Adny for
> pointing it.
> *including some minor issue.
>
> BTW, only passed build.
>
> include/linux/kthread.h | 45 +++++++++++++++++++++++++++++++++++----------
> kernel/kthread.c | 9 +++++++++
> 2 files changed, 44 insertions(+), 10 deletions(-)
Yong,
I have tested your patch with the following patch on top of yours. I
find the two patches together acceptable in testing in a machine with
both a PVR-350 card and a PVR-500 card installed.
Tested-by: Andy Walls <awalls@md.metrocast.net>
Signed-off-by: Andy Walls <awalls@md.metrocast.net>
Could you please author a [V3 PATCH] adding my changes? Since the
majority of the change is your work, it should be attributed to you as
the author.
About my additional changes:
I needed the explicit EXPORT_SYMBOL_GPL(__init_kthread_worker),
otherwise the build would fail, because the ivtv module had an
unresolved symbol.
I added the lockdep class name to make it easier to identify the ivtv
module's kthread worker's lock class. Now one can actually recognize
the lock class in lockdep output strings:
# cat lockdep | grep itv
ffffffffa0483a60 FD: 1 BD: 1 ......: (&itv->irq_worker)->lock
Thanks again.
Regards,
Andy
diff --git a/include/linux/kthread.h b/include/linux/kthread.h
index f8b3320..994564a 100644
--- a/include/linux/kthread.h
+++ b/include/linux/kthread.h
@@ -100,13 +100,15 @@ struct kthread_work {
# define DEFINE_KTHREAD_WORK_ONSTACK(work, fn) DEFINE_KTHREAD_WORK(work, fn)
#endif
-extern void __init_kthread_worker(struct kthread_worker *worker,
- struct lock_class_key *key);
+void __init_kthread_worker(struct kthread_worker *worker,
+ struct lock_class_key *key,
+ const char *lock_class_name);
#define init_kthread_worker(worker) \
do { \
static struct lock_class_key __key; \
- __init_kthread_worker((worker), &__key); \
+ __init_kthread_worker((worker), &__key, \
+ "(" #worker ")->lock"); \
} while (0)
#define init_kthread_work(work, fn) \
diff --git a/kernel/kthread.c b/kernel/kthread.c
index f760587..4657ebd 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -266,13 +266,15 @@ int kthreadd(void *unused)
}
void __init_kthread_worker(struct kthread_worker *worker,
- struct lock_class_key *key)
+ struct lock_class_key *key,
+ const char *lock_class_name)
{
spin_lock_init(&worker->lock);
- lockdep_set_class(&worker->lock, key);
+ lockdep_set_class_and_name(&worker->lock, key, lock_class_name);
INIT_LIST_HEAD(&worker->work_list);
worker->task = NULL;
}
+EXPORT_SYMBOL_GPL(__init_kthread_worker);
/**
* kthread_worker_fn - kthread function to process kthread_worker
next prev parent reply other threads:[~2010-12-22 0:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 12:49 [PATCH] kthread_worker: Initialize dynamically allocated spinlock properly for lockdep Andy Walls
2010-12-20 7:07 ` Yong Zhang
2010-12-20 9:28 ` Yong Zhang
2010-12-20 16:21 ` Tejun Heo
2010-12-21 1:54 ` Yong Zhang
2010-12-21 4:40 ` [V2 PATCH] kthread_work: Make lockdep happy Yong Zhang
2010-12-21 12:59 ` Tejun Heo
2010-12-21 13:25 ` Nicolas Mailhot
2010-12-21 16:07 ` Andy Walls
2010-12-22 0:39 ` Andy Walls [this message]
2010-12-22 3:12 ` Yong Zhang
2010-12-22 3:23 ` [V3 " Yong Zhang
2010-12-22 9:33 ` Tejun Heo
2010-12-20 17:16 ` [PATCH] kthread_worker: Initialize dynamically allocated spinlock properly for lockdep Andy Walls
2010-12-21 2:02 ` Yong Zhang
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=1292978393.2401.14.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=akpm@linux-foundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@redhat.com \
--cc=nicolas.mailhot@laposte.net \
--cc=tj@kernel.org \
--cc=yong.zhang0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox