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, 9 Nov 2022 23:40:13 -0500
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     Aaro Koskinen <aaro.koskinen@iki.fi>
Cc:     Linus Torvalds <torvalds@linux-foundation.org>,
        Paul Cercueil <paul@crapouillou.net>, vbabka@suse.cz,
        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, willy@infradead.org
Subject: Re: Deprecating and removing SLOB
Message-ID: <Y2yArTbOpKd6ASkd@mit.edu>
References: <K5M3LR.3O50LSSSY5L3@crapouillou.net>
 <CAHk-=wjBqwJk9RgfoBuM00T49M7uQiLnOvLST7L6v5rhS7fkDA@mail.gmail.com>
 <20221109234832.GE307514@darkstar.musicnaut.iki.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221109234832.GE307514@darkstar.musicnaut.iki.fi>
Precedence: bulk

On Thu, Nov 10, 2022 at 01:48:32AM +0200, Aaro Koskinen wrote:
> 
> Some of the reported SLOB issues have been actually real driver bugs,
> that go unnoticed when SLUB/SLAB are used (unless perhaps debug stuff
> is enabled). I'm not saying kernel should keep SLOB, but it's good at
> failing early when there is a bug. See e.g. commit 120ee599b5bf ("staging:
> octeon-usb: prevent memory corruption")

Out of curiosity, are these bugs that would have been found using
KASAN or some of the other kernel sanitizers and/or other debugging
tools we have at our disposal?

       		      	    	      	    	 - Ted