From: David Howells <dhowells@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: dhowells@redhat.com, Takashi Iwai <tiwai@suse.de>,
Ingo Molnar <mingo@elte.hu>,
Linux filesystem caching discussion list
<linux-cachefs@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>, oleg <oleg@redhat.com>
Subject: Re: Incorrect circular locking dependency?
Date: Tue, 04 Aug 2009 16:50:04 +0100 [thread overview]
Message-ID: <18723.1249401004@redhat.com> (raw)
In-Reply-To: <1249397486.7924.243.camel@twins>
Peter Zijlstra <peterz@infradead.org> wrote:
> Creating a new class for your second workqueue might help,
I only have one workqueue. The problem is there are two waitqueues, but
init_waitqueue_head() always sets q->lock to the same class.
> we'd have to pass a second key through __create_workqueue_key() and pass
> that into init_cpu_workqueue() and apply it to cwq->lock using
> lockdep_set_class() and co.
Actually, wouldn't just making init_cpu_workqueue() apply a class to
cwq->more_work that's common to all workqueues suffice? Or even, have
init_waitqueue_head() apply an alternate class to q->lock?
David
next prev parent reply other threads:[~2009-08-04 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 2:37 CacheFiles: Readpage failed on backing file Christian Kujau
2009-06-22 8:58 ` [Linux-cachefs] " David Howells
2009-06-22 14:54 ` Takashi Iwai
2009-06-22 15:21 ` David Howells
2009-06-22 15:45 ` Takashi Iwai
2009-07-07 7:21 ` Takashi Iwai
2009-07-07 13:00 ` David Howells
2009-07-07 13:05 ` Takashi Iwai
2009-07-27 14:37 ` Incorrect circular locking dependency? David Howells
2009-08-04 14:51 ` Peter Zijlstra
2009-08-04 15:50 ` David Howells [this message]
2009-08-04 16:08 ` Peter Zijlstra
2009-08-04 15:59 ` Oleg Nesterov
2009-08-04 17:23 ` [Linux-cachefs] CacheFiles: Readpage failed on backing file David Howells
2009-08-05 10:00 ` Takashi Iwai
2009-08-07 12:07 ` Takashi Iwai
2009-08-07 14:26 ` David Howells
2009-06-23 0:36 ` Christian Kujau
2009-06-23 7:49 ` Christian Kujau
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=18723.1249401004@redhat.com \
--to=dhowells@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tiwai@suse.de \
/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.