From: Steven King <sfking@fdwdc.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: [uClinux-dev] v3.15-rc1 slab allocator broken on m68knommu (coldfire)
Date: Wed, 16 Apr 2014 10:44:11 -0700 [thread overview]
Message-ID: <201404161044.11416.sfking@fdwdc.com> (raw)
In-Reply-To: <CAMuHMdV2zSWaDbHNv3QQeEgu26PQX9TWn7cHA=4U0YOK0bbExg@mail.gmail.com>
On Wednesday 16 April 2014 9:06:57 am Geert Uytterhoeven wrote:
> Hi Steven,
>
> On Wed, Apr 16, 2014 at 5:47 PM, Steven King <sfking@fdwdc.com> wrote:
> > --- a/mm/slab.c
> > +++ b/mm/slab.c
> > @@ -2572,13 +2572,13 @@ static void *alloc_slabmgmt(struct kmem_cache
> > *cachep, return freelist;
> > }
> >
> > -static inline freelist_idx_t get_free_obj(struct page *page, unsigned
> > char idx) +static inline freelist_idx_t get_free_obj(struct page *page,
> > unsigned int idx) {
> > return ((freelist_idx_t *)page->freelist)[idx];
> > }
> >
> > static inline void set_free_obj(struct page *page,
> > - unsigned char idx, freelist_idx_t
> > val) + unsigned int idx,
> > freelist_idx_t val) {
> > ((freelist_idx_t *)(page->freelist))[idx] = val;
> > }
> >
> >
> > then v3.15-rc1 will boot using the slab allocator.
>
> Is "idx" ever larger than 255?
>
> Gr{oetje,eeting}s,
Yes. If I stick
if (idx > 255)
pr_info("%s %d\n", __func__, idx);
in get_free_obj and set_free_obj and see values for idx up into the 400s.
next prev parent reply other threads:[~2014-04-16 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 0:45 Steven King
2014-04-16 0:19 ` Joonsoo Kim
2014-04-16 15:47 ` Steven King
2014-04-16 16:06 ` [uClinux-dev] " Geert Uytterhoeven
2014-04-16 17:44 ` Steven King [this message]
2014-04-17 1:49 ` Joonsoo Kim
2014-04-17 19:09 ` Steven King
2014-04-18 7:44 ` Joonsoo Kim
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=201404161044.11416.sfking@fdwdc.com \
--to=sfking@fdwdc.com \
--cc=geert@linux-m68k.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.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
Powered by JetHome