Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1329411ybl; Mon, 2 Dec 2019 01:40:42 -0800 (PST) X-Google-Smtp-Source: APXvYqxO2HrcNM2rbUJEG4hQg3Ehl+L1J4h5fAKaJkzsh1TqYDkoQDSgoaRmFrOAATlT1ga2prs9 X-Received: by 2002:a17:906:7e53:: with SMTP id z19mr10092144ejr.289.1575279642211; Mon, 02 Dec 2019 01:40:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575279642; cv=none; d=google.com; s=arc-20160816; b=uvNOvf92nXU+WfHGoB7+207xsCzW3EvDHWigbDhiK+oHT225sDFy26tLvSawdXajvQ U71qagNzS18KmNyFNr3Sygr613kQD5P2FvOk81ENuG207BfP0aLgDDGIHzL0HCsrqtWC BqDs8GjLyVN3sSSixKO9obGF/36NLjHZRxklaLCTMTPA2TGw3gd9w90l4K6I/rUWT7Wj ELzZ2SVu+HbUdQxB4zRZEF+t7gljNV/G4Te1jL4ZEKtBmusfQDOfkt05FV/iBAB053qu NRGhH/B32wlcAd4oOnUqDGLe9HE6vqGEAPmOFnC9RBhMbsBsqL8VpiDWqJk5HiEzEhn4 QxPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=mXfbyf/upZZBnp2Na+IfEomlLG1jmss1TGoDx2NxQIQ=; b=ilclTle7+rJOFtucmX0Un13pgi6+pPCJ3zyHbtJRUZXg0u36MDIRoUT857w9elvU9s 2X/wvpkkrlzZKAgn3mCAfmZrJO7YECCOi3PS2psp2mH+dlev1sjEPufKRG5iH+h7iU1k A0qVwXxPvG0TUm7d8+7KyMI4XcxRWr4SqQYx9nibjMfl7B7fssdOOZBUSeSxty712WrT aB8Uh+YD0mILdQa3AjYPu7TCeGLkbS7Q8VisEzxfOGOU1F2/WM0BSM0qxlrRC4LXddpA DkcUim/k9/+HAT8g2JuunAvPq2YYCE4w1QkNqE6yUdLx2rU/+Yrmiffld0C/346GiKr3 mqHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=n0RV9WdT; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d9si20461439ejw.65.2019.12.02.01.40.18; Mon, 02 Dec 2019 01:40:42 -0800 (PST) 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; dkim=pass header.i=@google.com header.s=20161025 header.b=n0RV9WdT; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726949AbfLBJjK (ORCPT + 99 others); Mon, 2 Dec 2019 04:39:10 -0500 Received: from mail-oi1-f196.google.com ([209.85.167.196]:39700 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726533AbfLBJjK (ORCPT ); Mon, 2 Dec 2019 04:39:10 -0500 Received: by mail-oi1-f196.google.com with SMTP id a67so13035144oib.6 for ; Mon, 02 Dec 2019 01:39:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mXfbyf/upZZBnp2Na+IfEomlLG1jmss1TGoDx2NxQIQ=; b=n0RV9WdTgP/91lc+kF3c1hS7d4WWWrogsPPm8GbAKwgUGZDWfNSMsLHfDSNULUz+/3 7KStCiTFPukPLmcx2yYjHcXQqugP6b5QxA8oVMlmW0Cehw+qFf3ylvbkYvolLUVxWNv/ 07BNhqp1hWwKembAaXypODfX8FFqZbn4E6tBKgVqkH+VoEYD228Dm1STa3WDKGPmUwcs D0aTPlSkrUelU0nVZ5IYRcyr05T2RSO5l+1XfCVDpAyryQ01JM7woVPYBTj8UNKQBLqz 389KeR/xrNtAkR9L2Wl1nmsOHDMWniIQbX/V2Mr7qbOFc3zQByOW+V7qKf5VIHk+0W6X 47zA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mXfbyf/upZZBnp2Na+IfEomlLG1jmss1TGoDx2NxQIQ=; b=jlNWNOsf6ki4D9fz8wbvQFN70vssbCCI9gIeMF+KKH04krOYmFc8GvfqFvliluNlXm 5qfE98lijZ7k7U8eaTk6B2O+d251++4hIrXZiBBSMJBXtKfpxHh6Ut7lFASLxbPAeEFm RPUUO2BrBzRr0ADrun63gUxCQEKdGC+JP8Od8wnsVDbF1xRjBo+uYtDxz77kw6Gn/IPX FKpM1EVcp1gqWx/aKAAcNhiJu3EOBOiSLvB7RW38D3b4LiQvU71WrSs/BFAT0Uizvth6 4z9LTatHmyq+JcD3sHCCy8THoheUHciezLq5BY80Ul4ZGVQd5Au1LhJpifn0TjxdfYOe YVPg== X-Gm-Message-State: APjAAAWu3MAClKI7F6DPY/LBoOHJzCo8DA1IOTfj3QYqoojt3mz1X+Jy YocXuH6qkAbnTMRKVBQxZ/BKCFLRRKzXisITDKgY1g== X-Received: by 2002:aca:d4c1:: with SMTP id l184mr23250358oig.172.1575279548664; Mon, 02 Dec 2019 01:39:08 -0800 (PST) MIME-Version: 1.0 References: <000001d5824d$c8b2a060$5a17e120$@codeaurora.org> <20191014101938.GB41626@lakrids.cambridge.arm.com> <0101016ec501966f-4b89bcda-49ba-45d3-b226-62538b901b04-000000@us-west-2.amazonses.com> In-Reply-To: <0101016ec501966f-4b89bcda-49ba-45d3-b226-62538b901b04-000000@us-west-2.amazonses.com> From: Marco Elver Date: Mon, 2 Dec 2019 10:38:57 +0100 Message-ID: Subject: Re: KCSAN Support on ARM64 Kernel To: sgrover@codeaurora.org Cc: Mark Rutland , Dmitry Vyukov , kasan-dev , LKML , "Paul E. McKenney" , Will Deacon , Andrea Parri , Alan Stern Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We're in the process of upstreaming KCSAN, which will simplify a lot of things including Arm64 support. So far KCSAN is not yet in mainline, but I assume when that happens (if things go well, very soon) it should be trivial to add Arm64 support based on Mark's prototype. Thanks, -- Marco On Mon, 2 Dec 2019 at 06:07, wrote: > > Hi All, > > Is there any update in Arm64 support of KCSAN. > > Regards, > Sachin Grover > > -----Original Message----- > From: Mark Rutland > Sent: Monday, 14 October, 2019 3:50 PM > To: Marco Elver > Cc: Dmitry Vyukov ; sgrover@codeaurora.org; kasan-dev= ; LKML ; Paul E.= McKenney ; Will Deacon ; And= rea Parri ; Alan Stern > Subject: Re: KCSAN Support on ARM64 Kernel > > 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=E2=80=99s say androi= d > > > > 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 t= o 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. >