Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933170AbdCGRsO (ORCPT ); Tue, 7 Mar 2017 12:48:14 -0500 Received: from mail-ua0-f175.google.com ([209.85.217.175]:33678 "EHLO mail-ua0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752255AbdCGRpp (ORCPT ); Tue, 7 Mar 2017 12:45:45 -0500 MIME-Version: 1.0 In-Reply-To: <7d14c37b-54ca-05d0-9fe6-62d82ac729fa@virtuozzo.com> References: <1eb0b1ba-3847-9bdc-8f4a-adcd34de3486@gmail.com> <7d14c37b-54ca-05d0-9fe6-62d82ac729fa@virtuozzo.com> From: Dmitry Vyukov Date: Tue, 7 Mar 2017 17:40:22 +0100 Message-ID: Subject: Re: kasan behavior when built with unsupported compiler To: Andrey Ryabinin Cc: Nikolay Borisov , Alexander Potapenko , LKML , kasan-dev , Kees Cook Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 480 Lines: 16 On Tue, Mar 7, 2017 at 5:26 PM, Andrey Ryabinin wrote: > > > On 03/07/2017 06:54 PM, Dmitry Vyukov wrote: > >> >> Hi, >> >> Re the message that kasan is not supported while it's still enabled in the end. >> I think it's an issue related to gcc plugins. Originally kasan was >> supported with 5.0+ thus the message. However, later we extended this >> support to 4.5+ with gcc plugins. > > You made this up, we don't have such plugin. Right. It was KCOV.