Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4353421ybp; Mon, 14 Oct 2019 03:20:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqxTgpjwWnp935it8mC9BSxy6F7MvXsQGKRJ1aqxRbxDu67jhbtss8wYnL3gbzLSmfHUUwwj X-Received: by 2002:a17:906:6882:: with SMTP id n2mr28581071ejr.48.1571048454094; Mon, 14 Oct 2019 03:20:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571048454; cv=none; d=google.com; s=arc-20160816; b=ME9pJQ8lh40zatjLEUUMzZM/hmVuQa76802o68r6WHoVWyioNqyNOk2mDuVHlm8yiV CaypPbWjClKmi9nn1x5uYUmG1jDr58Ntf+qUXlcmvbSAEFg4rDXxPRDesV5V/qq6/Kaa fz6/dLM/XwAPXuG71FVVV200N6Kjp8haXrAnyM8Z26Ndl25ie06Ev2lU51J8grUpgqOU EMt6cM633h8vYUg5juyXB1fsa6KE1lLryRjOhW0xkMPHbXviMaGZ4rTiwnDVns4+xBrQ AIlnoCaTH7GyR0u7lglgN5Nl+gwHzLPUrWdli6pOJqXjvx8l/YuQNeh+MXqkUydbevAc Vd1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=SjYBNYn+6Lqo5IA7ZbINeGXg7gKAFbqoE+NHEJwg+bQ=; b=qWrR9/6RBdKqXL7Djn7AIc0MfiEX7AiqtD38gQ8tlk+++aJTHO2eRskDJa69Ady9Lx BtPIifQgQITfTesH1DY+Z9iMnYUrpygf27KcRFhvFzZ/hnOf1GOH/Fz1Y6gkDam/N5zE FrWsxCY+g61RNaiGFqOIz+smEujKAwskPYFJ6bhrKoSm71patTmsjscbS9yvTQqdyTOt rPyzvYqYSmLYT8gNdmVC7VPYSQmXq4BHxLJWu0bv2JrAsqBHliyCg1doS6uYdoIwOM1s pVsAGLTXLe45ONLzXmddDZSP9PRzl1ggqANRQzKFpF7wLjQuR6FvzsRD6OMoAonER0fH FWWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g10si10465733ejc.424.2019.10.14.03.20.30; Mon, 14 Oct 2019 03:20:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731355AbfJNKTm (ORCPT + 99 others); Mon, 14 Oct 2019 06:19:42 -0400 Received: from foss.arm.com ([217.140.110.172]:39672 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730860AbfJNKTm (ORCPT ); Mon, 14 Oct 2019 06:19:42 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 97E38337; Mon, 14 Oct 2019 03:19:41 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5E53A3F718; Mon, 14 Oct 2019 03:19:40 -0700 (PDT) Date: Mon, 14 Oct 2019 11:19:38 +0100 From: Mark Rutland To: Marco Elver Cc: Dmitry Vyukov , sgrover@codeaurora.org, kasan-dev , LKML , "Paul E. McKenney" , Will Deacon , Andrea Parri , Alan Stern Subject: Re: KCSAN Support on ARM64 Kernel Message-ID: <20191014101938.GB41626@lakrids.cambridge.arm.com> References: <000001d5824d$c8b2a060$5a17e120$@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 14, 2019 at 11:09:40AM +0200, Marco Elver wrote: > On Mon, 14 Oct 2019 at 10:40, Dmitry Vyukov wrote: > > > > On Mon, Oct 14, 2019 at 7:11 AM wrote: > > > > > > Hi Dmitry, > > > > > > I am from Qualcomm Linux Security Team, just going through KCSAN > > > and found that there was a thread for arm64 support > > > (https://lkml.org/lkml/2019/9/20/804). > > > > > > Can you please tell me if KCSAN is supported on ARM64 now? Can I > > > just rebase the KCSAN branch on top of our let’s say android > > > mainline kernel, enable the config and run syzkaller on that for > > > finding race conditions? > > > > > > It would be very helpful if you reply, we want to setup this for > > > finding issues on our proprietary modules that are not part of > > > kernel mainline. > > > > > > Regards, > > > > > > Sachin Grover > > > > +more people re KCSAN on ARM64 > > KCSAN does not yet have ARM64 support. Once it's upstream, I would > expect that Mark's patches (from repo linked in LKML thread) will just > cleanly apply to enable ARM64 support. Once the core kcsan bits are ready, I'll rebase the arm64 patch atop. I'm expecting some things to change as part of review, so it'd be great to see that posted ASAP. For arm64 I'm not expecting major changes (other than those necessary to handle the arm64 atomic rework that went in to v5.4-rc1) FWIW, I was able to run Syzkaller atop of my arm64/kcsan branch, but it's very noisy as it has none of the core fixes. Thanks, Mark.