[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Oct 2017 00:14:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Tom Gall <tom.gall@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
Shuah Khan <shuahkh@....samsung.com>, patches@...nelci.org,
Ben Hutchings <ben.hutchings@...ethink.co.uk>,
linux- stable <stable@...r.kernel.org>
Subject: Re: [PATCH 4.9 000/104] 4.9.54-stable review
On Tue, Oct 10, 2017 at 11:39:09AM -0700, Guenter Roeck wrote:
> On Tue, Oct 10, 2017 at 05:33:04PM +0200, Greg Kroah-Hartman wrote:
> > Ick, not good, why not? Surely you enable all of the options you can
> > for your hardware, right? And enabling stuff like this is good no
> > matter what...
What I said about KASAN in the other mail applies more generally - some
of the debug options are very low overhead but that's not always the
case, especially when running on lower end hardware.
> FWIW, I don't enable CONFIG_KASAN or my qemu test runs either, simply because
> enabling it makes images all but impossible to run in qemu. Whatever KASAN
> does, it seems to completely defeat qemu.
It's much slower and uses a lot more memory, I'd guess either of those
could be a big issue.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists