From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: [PATCH]slub: fix bad scope checking
Date: Thu, 01 Apr 2010 17:32:30 +0800 [thread overview]
Message-ID: <1270114350.2078.111.camel@ymzhang.sh.intel.com> (raw)
Function init_kmem_cache_nodes is incorrect when checking upper limitation
of kmalloc_caches.
The patch against latest tip/master fixes it.
From: Zhang, Yanmin <yanmin_zhang@linux.intel.com>
---
--- linux-2.6/mm/slub.c 2010-04-01 17:01:21.091999999 +0800
+++ linux-2.6_slub/mm/slub.c 2010-04-01 17:04:34.876000010 +0800
@@ -2153,7 +2153,7 @@ static int init_kmem_cache_nodes(struct
int local_node;
if (slab_state >= UP && (s < kmalloc_caches ||
- s > kmalloc_caches + KMALLOC_CACHES))
+ s >= kmalloc_caches + KMALLOC_CACHES))
local_node = page_to_nid(virt_to_page(s));
else
local_node = 0;
next reply other threads:[~2010-04-01 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 9:32 Zhang, Yanmin [this message]
2010-04-01 16:00 ` [PATCH]slub: fix bad scope checking Christoph Lameter
2010-04-02 7:03 ` Pekka Enberg
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=1270114350.2078.111.camel@ymzhang.sh.intel.com \
--to=yanmin_zhang@linux.intel.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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;
as well as URLs for NNTP newsgroup(s).