[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210212121610.ff05a7bb37f97caef97dc924@linux-foundation.org>
Date: Fri, 12 Feb 2021 12:16:10 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrey Konovalov <andreyknvl@...gle.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Will Deacon <will.deacon@....com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Marco Elver <elver@...gle.com>,
Peter Collingbourne <pcc@...gle.com>,
Evgenii Stepanov <eugenis@...gle.com>,
Branislav Rankov <Branislav.Rankov@....com>,
Kevin Brodsky <kevin.brodsky@....com>,
Christoph Hellwig <hch@...radead.org>,
kasan-dev@...glegroups.com, linux-arm-kernel@...ts.infradead.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH mm] kasan: export HW_TAGS symbols for KUnit tests
On Fri, 12 Feb 2021 21:08:52 +0100 Andrey Konovalov <andreyknvl@...gle.com> wrote:
> Currently, building KASAN-KUnit tests as a module fails with:
>
> ERROR: modpost: "mte_enable_kernel" [lib/test_kasan.ko] undefined!
> ERROR: modpost: "mte_set_report_once" [lib/test_kasan.ko] undefined!
>
> This change adds KASAN wrappers for mte_enable_kernel() and
> mte_set_report_once() and only defines and exports them when KASAN-KUnit
> tests are enabled.
>
> The wrappers aren't defined when tests aren't enabled to avoid misuse.
> The mte_() functions aren't exported directly to avoid having low-level
> KASAN ifdefs in the arch code.
>
Please confirm that this is applicable to current Linus mainline?
Today is pretty much the last day for getting material into 5.11, and
this patch has been churning somewhat.
So I think it would be better to merge this into 5.12-rc1, with a
cc:stable so it goes into 5.11.1.
For which we'll need a Fixes:, please?
Powered by blists - more mailing lists