From: David Miller <davem@davemloft.net>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org, iamjoonsoo.kim@lge.com,
sparclinux@vger.kernel.org, hannes@cmpxchg.org, cl@linux.com,
penberg@kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] slab: Fix off by one in object max number tests.
Date: Mon, 05 May 2014 17:08:55 -0400 (EDT) [thread overview]
Message-ID: <20140505.170855.814445464231092040.davem@davemloft.net> (raw)
In-Reply-To: <20140505210507.GA5130@ravnborg.org>
From: Sam Ravnborg <sam@ravnborg.org>
Date: Mon, 5 May 2014 23:05:07 +0200
> On Mon, May 05, 2014 at 04:57:56PM -0400, David Miller wrote:
>> From: David Miller <davem@davemloft.net>
>> Date: Mon, 05 May 2014 16:20:04 -0400 (EDT)
>>
>> >
>> > 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.
>>
>> It turns out that after some more testing, I'm still getting spinlock
>> debugging problems with this fix applied.
>>
>> The change is still very much correct I think, however.
>
> There is a related patch in this area which I think is not yet applied.
>
> See: https://lkml.org/lkml/2014/4/18/28
>
> Maybe this is realted.
Thanks, I'm testing with that patch added as well.
next prev parent reply other threads:[~2014-05-05 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 20:20 David Miller
2014-05-05 20:57 ` David Miller
2014-05-05 21:05 ` Sam Ravnborg
2014-05-05 21:08 ` David Miller [this message]
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.170855.814445464231092040.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=sam@ravnborg.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®