linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: vbabka@suse.cz
Cc: 42.hyeyoo@gmail.com, akpm@linux-foundation.org,
	catalin.marinas@arm.com, cl@linux.com, iamjoonsoo.kim@lge.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	penberg@kernel.org, rientjes@google.com, rkovhaev@gmail.com,
	roman.gushchin@linux.dev, torvalds@linux-foundation.org,
	willy@infradead.org
Subject: Re: Deprecating and removing SLOB
Date: Wed, 09 Nov 2022 20:56:08 +0000	[thread overview]
Message-ID: <K5M3LR.3O50LSSSY5L3@crapouillou.net> (raw)

Hi Vlastimil,

I was actually using SLOB until recently for a device flasher program 
(kernel + initramfs + dtb, booted over USB) for Ingenic SoCs. I picked 
SLOB just because it said "embedded systems" in menuconfig and some of 
my boards have as little as 32 MiB RAM.

It worked fine on some boards, but on others it had about a 25% chance 
of booting, and 75% chance of hanging at boot. I tried printk-debugging 
it, and was coming to the conclusion that it's memory corruption of 
some sort.

Then I switched to SLUB and all the problems are gone. Same with SLAB.

So while I can't say for sure that SLOB is broken (it might be 
triggering a bug somewhere else), I am highly suspicious that it is.

So yeah... axe it.

Cheers,
-Paul




             reply	other threads:[~2022-11-09 20:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 20:56 Paul Cercueil [this message]
2022-11-09 21:39 ` Deprecating and removing SLOB Linus Torvalds
2022-11-09 23:48   ` Aaro Koskinen
2022-11-09 23:51     ` Aaro Koskinen
2022-11-10  4:40     ` Theodore Ts'o
2022-11-10  7:31       ` Vlastimil Babka
2022-11-10  7:54         ` Feng Tang
2022-11-10 16:20         ` Matthew Wilcox
2022-11-11  9:37           ` David Laight
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 15:55 Vlastimil Babka
2022-11-08 18:18 ` Christophe Leroy
2022-11-08 19:17   ` Andrew Morton
2022-11-08 18:46 ` Roman Gushchin
2022-11-08 20:13   ` Yosry Ahmed
2022-11-09  9:09     ` Vlastimil Babka
2022-11-08 21:44 ` Pasha Tatashin
2022-11-09  9:00   ` Vlastimil Babka
2022-11-09 15:50     ` Aaro Koskinen
2022-11-09 16:45       ` Geert Uytterhoeven
2022-11-09 17:45       ` Mike Rapoport
2022-11-09 21:16       ` Janusz Krzysztofik
2022-11-09 17:57   ` Conor.Dooley
2022-11-09 23:00     ` Damien Le Moal
2022-11-11 10:25       ` Vlastimil Babka
2022-11-12  1:40         ` Damien Le Moal
2022-11-11 10:33   ` Vlastimil Babka
2022-11-11 20:46     ` Conor Dooley
2022-11-12  1:40       ` Damien Le Moal
2022-11-14  1:55       ` Damien Le Moal
2022-11-14  5:48         ` Damien Le Moal
2022-11-14  9:36           ` Vlastimil Babka
2022-11-14 11:35             ` Damien Le Moal
2022-11-14 14:47               ` Hyeonggon Yoo
2022-11-15  4:24                 ` Damien Le Moal
2022-11-15  4:28                   ` Damien Le Moal
2022-11-16  7:57                     ` Matthew Wilcox
2022-11-16  8:02                       ` Damien Le Moal
2022-11-16 17:51                   ` Vlastimil Babka
2022-11-17  0:22                     ` Damien Le Moal
2022-11-21  4:30                     ` Damien Le Moal
2022-11-21 17:02                       ` Vlastimil Babka
2022-11-14 11:50             ` Hyeonggon Yoo

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=K5M3LR.3O50LSSSY5L3@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rkovhaev@gmail.com \
    --cc=roman.gushchin@linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).