On Thu, Aug 27, 2020 at 12:45 PM Catalin Marinas <catalin.marinas@xxxxxxx> wrote: > > On Fri, Aug 14, 2020 at 07:27:13PM +0200, Andrey Konovalov wrote: > > diff --git a/mm/kasan/mte.c b/mm/kasan/mte.c > > new file mode 100644 > > index 000000000000..43b7d74161e5 > > --- /dev/null > > +++ b/mm/kasan/mte.c > > Since this is an arm64-specific kasan backend, I wonder whether it makes > more sense to keep it under arch/arm64 (mte-kasan.c). I'm not sure if we do. I'd rather keep everything together, spreading the implementation around the kernel is inconvenient. We already have software tag-based KASAN implementation (which is also arm64-specific) in the common code. We could, perhaps, rename mte.c into something more generic, with other potential future hardware modes in mind. > > diff --git a/mm/kasan/report_mte.c b/mm/kasan/report_mte.c > > new file mode 100644 > > index 000000000000..dbbf3aaa8798 > > --- /dev/null > > +++ b/mm/kasan/report_mte.c > > Same for this one.