[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2yArTbOpKd6ASkd@mit.edu>
Date: Wed, 9 Nov 2022 23:40:13 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: Aaro Koskinen <aaro.koskinen@....fi>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Paul Cercueil <paul@...pouillou.net>, vbabka@...e.cz,
42.hyeyoo@...il.com, akpm@...ux-foundation.org,
catalin.marinas@....com, cl@...ux.com, iamjoonsoo.kim@....com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
penberg@...nel.org, rientjes@...gle.com, rkovhaev@...il.com,
roman.gushchin@...ux.dev, willy@...radead.org
Subject: Re: Deprecating and removing SLOB
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
Powered by blists - more mailing lists