From: Christoph Lameter <cl@linux.com>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: akpm@linux-foundation.org, rientjes@google.com,
penberg@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slub: fix false-positive lockdep warning in free_partial()
Date: Tue, 4 Feb 2014 14:44:43 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.10.1402041444140.11222@nuc> (raw)
In-Reply-To: <1391517397-6142-1-git-send-email-vdavydov@parallels.com>
On Tue, 4 Feb 2014, Vladimir Davydov wrote:
> Although this cannot actually result in a race, because on cache
> destruction there should not be any concurrent frees or allocations from
> the cache, let's add spin_lock/unlock to free_partial() just to keep
> lockdep happy.
Please add a comment that says this in the source so we know why this was
added.
next prev parent reply other threads:[~2014-02-04 20:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 12:36 Vladimir Davydov
2014-02-04 20:44 ` Christoph Lameter [this message]
2014-02-05 0:57 ` David Rientjes
2014-02-05 6:34 ` Vladimir Davydov
2014-02-05 6:44 ` [PATCH v2] " Vladimir Davydov
2014-02-05 8:01 ` David Rientjes
2014-02-05 8:12 ` Vladimir Davydov
2014-02-05 8:15 ` [PATCH v3] " Vladimir Davydov
2014-02-05 8:22 ` David Rientjes
2014-02-05 19:30 ` Christoph Lameter
2014-02-05 19:58 ` Steven Rostedt
2014-02-05 20:32 ` David Rientjes
2014-02-05 20:58 ` Steven Rostedt
2014-02-05 21:07 ` David Rientjes
2014-02-05 21:19 ` Steven Rostedt
2014-02-05 21:25 ` David Rientjes
2014-02-05 21:31 ` Steven Rostedt
2014-02-05 21:35 ` David Rientjes
2014-02-05 20:42 ` Christoph Lameter
2014-02-05 20:55 ` Steven Rostedt
2014-02-06 8:38 ` Peter Zijlstra
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=alpine.DEB.2.10.1402041444140.11222@nuc \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vdavydov@parallels.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
all inboxes | Powered by JetHome®