From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Josh Cartwright <joshc@ni.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
linux-rt-users@vger.kernel.org
Subject: Re: [4.4.4-rt11] Possiblie recursive locking detected in kswapd / mb_cache_shrink_scan()
Date: Wed, 30 Mar 2016 10:16:26 +0200 [thread overview]
Message-ID: <56FB8B5A.8@linutronix.de> (raw)
In-Reply-To: <20160329231434.GO28102@jcartwri.amer.corp.natinst.com>
On 03/30/2016 01:14 AM, Josh Cartwright wrote:
> On Tue, Mar 29, 2016 at 01:20:02PM -0500, Josh Cartwright wrote:
>> On Tue, Mar 29, 2016 at 05:04:44PM +0200, Sebastian Andrzej Siewior wrote:
>
> The problem isn't that _all_ instances of the hlist_bl_head will share a
> lockdep class...it's that instances which are INIT_HLIST_BL_HEAD()'d _within
> the same compilation unit_ will share a lockdep class.
no, that is okay. No, that is actually all good. I must have mixed up
the lock inits. Sorry for the confusion. After looking at it again it
is all good.
Please send a proper patch and I add it to the queue.
>
>
> Josh
>
Sebastian
next prev parent reply other threads:[~2016-03-30 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 21:00 [4.4.4-rt11] Possiblie recursive locking detected in kswapd / mb_cache_shrink_scan() Luis Claudio R. Goncalves
2016-03-19 8:33 ` Thomas Gleixner
2016-03-21 13:34 ` Luis Claudio R. Goncalves
2016-03-21 14:40 ` Josh Cartwright
2016-03-21 20:47 ` Luis Claudio R. Goncalves
2016-03-29 15:04 ` Sebastian Andrzej Siewior
2016-03-29 18:20 ` Josh Cartwright
2016-03-29 23:14 ` Josh Cartwright
2016-03-30 8:16 ` Sebastian Andrzej Siewior [this message]
2016-03-31 5:04 ` [PATCH] list_bl: fixup bogus lockdep warning Josh Cartwright
2016-04-01 10:46 ` Sebastian Andrzej Siewior
2016-04-01 10:49 ` Sebastian Andrzej Siewior
2016-04-01 17:02 ` Josh Cartwright
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=56FB8B5A.8@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=joshc@ni.com \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.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.