[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <86d982368a85ab9dde17e52b45e77f5f76efea08.camel@sipsolutions.net>
Date: Mon, 01 Dec 2025 11:56:05 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Baoquan He <bhe@...hat.com>, linux-mm@...ck.org
Cc: ryabinin.a.a@...il.com, andreyknvl@...il.com, glider@...gle.com,
dvyukov@...gle.com, vincenzo.frascino@....com, akpm@...ux-foundation.org,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, elver@...gle.com, sj@...nel.org,
lorenzo.stoakes@...cle.com, snovitoll@...il.com,
christophe.leroy@...roup.eu, linux-um@...ts.infradead.org
Subject: Re: [PATCH v4 11/12] arch/um: don't initialize kasan if it's
disabled
On Fri, 2025-11-28 at 11:33 +0800, Baoquan He wrote:
> And also do the kasan_arg_disabled chekcing before kasan_flag_enabled
^^^^^^^^
typo
> enabling to make sure kernel parameter kasan=on|off has been parsed.
But I'm not sure how to understand that sentence.
And I have no idea what to do with this patch, with it being random CC
of the middle of the series.
johannes
Powered by blists - more mailing lists