Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1340247ybn; Wed, 2 Oct 2019 14:40:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqyZKiN/Kc9EnxBJNygh7zLw2KREDXOETfyWYx5AyRiS3fXMFTuiuBSW5k8Y/lNVbXN7dmzt X-Received: by 2002:a17:906:6c8:: with SMTP id v8mr5113209ejb.40.1570052443329; Wed, 02 Oct 2019 14:40:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570052443; cv=none; d=google.com; s=arc-20160816; b=yNa5xhCftQdf8xu8lk6tdb9M6XUbKHF/ZaYJn1RZXVjKML8OzjE3HHdRLw5dqkP1Ir 5O1UH2IbPIFJ8XkTrkOb6stjHr8lrD0tG/0t+XrLNDeN0/Vf/GjkKqYyc7ZCvCCQkEJz LueTzY9LZq1ep3ikUd9m7BSQYIuNTKXJunLNgnwN1jw9ps/Gcp96VvozhEEP5ny/iPzs kwNTLa1Uyphsb4xyQ+IiQ30DwtT44ssH5HoKFXU4CZcyj1fLN0gkkmuJTydJ9q2sY5mv vz1lBJLB29UmfRybRcG0PaKXA27LMFgegysBUKr3sbJ/pbbARUa2OgBtLdTAS5E7kRBU h2IA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=8UdMjUT2pdLGE8ndpyA/9BXAvjXXhiUaO/cTeSeGp6c=; b=QtZZ3ujyNo/gwEh6GWpbeKW9jl51mnu6Vzt31iSbbPgop59NmJFs7hToiOycf3dwPt 6ArECLvYsAekHI/qkBpQUuXx4myghYNwbWqDjKyWMakvocfK2L+wkSTtYiS8mqJR82Dd IV0MaNik5IYr2S6lhxEXONmJBIM4o9vJdDjGgOljIMw3FkK+1PSYGVYQu0zcn1ANF3zQ MIvUuDEVOvi2TlIv4+Ub3CiDOMqUjEKLXk+yGDgnk+dL5DAYF7nFWBrHXSSe2ijGFLFn O7xk9f6cZy7PddAg+Gbfro/aYPsQ0DvclgqpyK7RkEmbFDm7Yt8xnZW1pU11sv3XiasA NWzA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=DbBnVOau; 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 v8si259183edi.22.2019.10.02.14.40.19; Wed, 02 Oct 2019 14:40:43 -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; dkim=pass header.i=@google.com header.s=20161025 header.b=DbBnVOau; 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 S1727495AbfJBTwL (ORCPT + 99 others); Wed, 2 Oct 2019 15:52:11 -0400 Received: from mail-oi1-f196.google.com ([209.85.167.196]:33055 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726207AbfJBTwL (ORCPT ); Wed, 2 Oct 2019 15:52:11 -0400 Received: by mail-oi1-f196.google.com with SMTP id e18so498932oii.0 for ; Wed, 02 Oct 2019 12:52:10 -0700 (PDT) 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; bh=8UdMjUT2pdLGE8ndpyA/9BXAvjXXhiUaO/cTeSeGp6c=; b=DbBnVOauShbcm7l0q/J9/fw2wbdf91+kUqz5f43RUfHDMuXQWrtNZXQqeRJcDPUaOf hkXW8W33rQxI7uhJ3o430fKOCcpBUY/yXh+twebiRcH3aCqth0om2mK93lhekrhCyyqP uHrNFujwMRsNd+jBxEKVmsSyq4uQrUZeza0bgPgrR9J8NI2vYDUM19jZ0ipHWWTsD4R1 JCXdyCWDfxYXK5aOq7uaz7f8OyO78Kkf3oGJmlJQfI69K68zGZrSAD5LNGK5p+30GbCZ fpHEulhvc78VthYynGANKy5J2Bn4/180s093P+J4wbKYH7FuXLHzLu43PZu1dLA9EZNQ VUCg== 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; bh=8UdMjUT2pdLGE8ndpyA/9BXAvjXXhiUaO/cTeSeGp6c=; b=SsC5UmGyg0SuJOAnpEADpDbyjn8ipJJ8unyK8WoWebiRbGXpGTH8+qEI+jTvnZRPtV ftKSglIqsh4wTVmuJhzEwVTNE/RJXpictB74MKHDmmpBVb46uJBn3KB0lvspYIfP1KKw 6k1K+f3hyPTvjBiyv81ouCC7NmeOhHORgoT5nU83ld72zDyN8beqpZJCH47a7OQ+9/7U 0I293P/VuVSM+cj40vXQiFAmKwxcpM+Sv5Enmip4Yg/3LnHvKFEbMli+O3o6bciZIpVT 6hBO+b7Thi/71s2YMnzcwSSNFCR0vvU/18mMJc22U2OyIouod0r0d3KrHZros7+5+C7G 3qkg== X-Gm-Message-State: APjAAAVplBiQwlreJVbl8ZnCO7XTSGCeaPuYPDFRUk6D6xEN+fjua8ma ydk6tB7/PkKPqlMXevY6dqhzRqT1S1wlNKnDbC07ig== X-Received: by 2002:a05:6808:13:: with SMTP id u19mr4279200oic.83.1570045929963; Wed, 02 Oct 2019 12:52:09 -0700 (PDT) MIME-Version: 1.0 References: <20191001211948.GA42035@google.com> In-Reply-To: <20191001211948.GA42035@google.com> From: Marco Elver Date: Wed, 2 Oct 2019 21:51:58 +0200 Message-ID: Subject: Re: Kernel Concurrency Sanitizer (KCSAN) To: Joel Fernandes Cc: kasan-dev , LKML , Dmitry Vyukov , Andrey Konovalov , Alexander Potapenko , "Paul E. McKenney" , Paul Turner , Daniel Axtens , Anatol Pomazau , Will Deacon , Andrea Parri , Alan Stern , LKMM Maintainers -- Akira Yokosawa , Nicholas Piggin , Boqun Feng , Daniel Lustig , Jade Alglave , Luc Maranget Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Joel, On Tue, 1 Oct 2019 at 23:19, Joel Fernandes wrote: > > On Fri, Sep 20, 2019 at 04:18:57PM +0200, Marco Elver wrote: > > Hi all, > > > > We would like to share a new data-race detector for the Linux kernel: > > Kernel Concurrency Sanitizer (KCSAN) -- > > https://github.com/google/ktsan/wiki/KCSAN (Details: > > https://github.com/google/ktsan/blob/kcsan/Documentation/dev-tools/kcsan.rst) > > > > To those of you who we mentioned at LPC that we're working on a > > watchpoint-based KTSAN inspired by DataCollider [1], this is it (we > > renamed it to KCSAN to avoid confusion with KTSAN). > > [1] http://usenix.org/legacy/events/osdi10/tech/full_papers/Erickson.pdf > > > > In the coming weeks we're planning to: > > * Set up a syzkaller instance. > > * Share the dashboard so that you can see the races that are found. > > * Attempt to send fixes for some races upstream (if you find that the > > kcsan-with-fixes branch contains an important fix, please feel free to > > point it out and we'll prioritize that). > > > > There are a few open questions: > > * The big one: most of the reported races are due to unmarked > > accesses; prioritization or pruning of races to focus initial efforts > > to fix races might be required. Comments on how best to proceed are > > welcome. We're aware that these are issues that have recently received > > attention in the context of the LKMM > > (https://lwn.net/Articles/793253/). > > * How/when to upstream KCSAN? > > Looks exciting. I think based on our discussion at LPC, you mentioned > one way of pruning is if the compiler generated different code with _ONCE > annotations than what would have otherwise been generated. Is that still on > the table, for the purposing of pruning the reports? This might be interesting at first, but it's not entirely clear how feasible it is. It's also dangerous, because the real issue would be ignored. It may be that one compiler version on a particular architecture generates the same code, but any change in compiler or architecture and this would no longer be true. Let me know if you have any more ideas. Best, -- Marco > Also appreciate a CC on future patches as well. > > thanks, > > - Joel > > > > > > Feel free to test and send feedback. > > > > Thanks, > > -- Marco > > -- > You received this message because you are subscribed to the Google Groups "kasan-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to kasan-dev+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/kasan-dev/20191001211948.GA42035%40google.com.