Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 09 Nov 2022 20:56:08 +0000
From:   Paul Cercueil <paul@crapouillou.net>
Subject: Re: Deprecating and removing SLOB
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
Message-Id: <K5M3LR.3O50LSSSY5L3@crapouillou.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Precedence: bulk

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