From: David Miller <davem@davemloft.net>
To: linux-kernel@vger.kernel.org
Cc: iamjoonsoo.kim@lge.com, sparclinux@vger.kernel.org,
hannes@cmpxchg.org, cl@linux.com, penberg@kernel.org,
torvalds@linux-foundation.org
Subject: [PATCH] slab: Fix off by one in object max number tests.
Date: Mon, 05 May 2014 16:20:04 -0400 (EDT) [thread overview]
Message-ID: <20140505.162004.1797345518474659123.davem@davemloft.net> (raw)
If freelist_idx_t is a byte, SLAB_OBJ_MAX_NUM should be 255 not 256,
and likewise if freelist_idx_t is a short, then it should be 65535 not
65536.
Fixes: a41adfa ("slab: introduce byte sized index for the freelist of a slab")
Signed-off-by: David S. Miller <davem@davemloft.net>
---
This was leading to all kinds of random crashes on sparc64 where PAGE_SIZE
is 8192. One problem shown was that if spinlock debugging was enabled,
we'd get deadlocks in copy_pte_range() or do_wp_page() with the same cpu
already holding a lock it shouldn't hold, or the lock belonging to a
completely unrelated process.
diff --git a/mm/slab.c b/mm/slab.c
index 388cb1a..37de3a7 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -166,7 +166,7 @@ typedef unsigned char freelist_idx_t;
typedef unsigned short freelist_idx_t;
#endif
-#define SLAB_OBJ_MAX_NUM (1 << sizeof(freelist_idx_t) * BITS_PER_BYTE)
+#define SLAB_OBJ_MAX_NUM ((1 << sizeof(freelist_idx_t) * BITS_PER_BYTE) - 1)
/*
* true if a page was allocated from pfmemalloc reserves for network-based
next reply other threads:[~2014-05-05 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 20:20 David Miller [this message]
2014-05-05 20:57 ` David Miller
2014-05-05 21:05 ` Sam Ravnborg
2014-05-05 21:08 ` David Miller
2014-05-06 3:25 ` David Miller
2014-05-06 3:32 ` Linus Torvalds
2014-05-06 3:46 ` Linus Torvalds
2014-05-06 3:48 ` David Miller
2014-05-06 4:04 ` 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=20140505.162004.1797345518474659123.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®