Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <f6efb2f36fc1f40eb22df027e6bc956cac71745e.1615498565.git.andreyknvl@google.com>
 <da296c4fe645f724922b691019e9e578e1834557.1615498565.git.andreyknvl@google.com>
 <CANpmjNP3bHe2h1=-W7r-64Vg9vr9vREzY0M97uh_QRDr3tVEYQ@mail.gmail.com>
In-Reply-To: <CANpmjNP3bHe2h1=-W7r-64Vg9vr9vREzY0M97uh_QRDr3tVEYQ@mail.gmail.com>
From:   Andrey Konovalov <andreyknvl@google.com>
Date:   Fri, 12 Mar 2021 14:51:56 +0100
Message-ID: <CAAeHK+xHeGQ8FSddfFpLrq+5YHoRZ+5KZr2zB+fzCssSbE_=bg@mail.gmail.com>
Subject: Re: [PATCH 02/11] kasan: docs: update overview section
To:     Marco Elver <elver@google.com>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Alexander Potapenko <glider@google.com>,
        Andrey Ryabinin <aryabinin@virtuozzo.com>,
        Dmitry Vyukov <dvyukov@google.com>,
        kasan-dev <kasan-dev@googlegroups.com>,
        Linux Memory Management List <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Mar 12, 2021 at 11:18 AM Marco Elver <elver@google.com> wrote:
>
> > -Currently generic KASAN is supported for the x86_64, arm, arm64, xtensa, s390
> > +The hardware KASAN mode (#3) relies on hardware to perform the checks but
> > +still requires a compiler version that supports memory tagging instructions.
> > +This mode is supported in Clang 11+.
>
> Doesn't HW_TAGS mode work with GCC as well? While the sentence doesn't
> say "exclusively", the mention of Clang 11+ makes me think it's only
> Clang.

I never tried it with GCC until just now. But looks like it works.
Will add GCC here, thanks!