From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D93D8C54EE9 for ; Wed, 7 Sep 2022 17:44:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229978AbiIGRoR (ORCPT ); Wed, 7 Sep 2022 13:44:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46428 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229984AbiIGRoN (ORCPT ); Wed, 7 Sep 2022 13:44:13 -0400 Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A9AFBD771 for ; Wed, 7 Sep 2022 10:44:09 -0700 (PDT) Received: by mail-yb1-xb30.google.com with SMTP id 202so18022106ybe.13 for ; Wed, 07 Sep 2022 10:44:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=N+KH0bFLs52wGl8kzsXXlEDsvOIn0U7dgBgJ6SkG/So=; b=Aoe02Mj5izznE3nsHvWbwiuwxP/svNeaiait61fx8gNuWRmRXcKHoL9Adoed44LPmC 7Px5DVwpwvu1FVTGhpVAqCOmCYjY1c8lttl3+JoBw+FZ6QdfI6mW+Se/C1MVbE9CpovM 47KweB6a35vnC0ihHF8MH1nX54sLf60teydGpUbqN4V7BLUGwLbH337GsAlCli2d/aOr MC8ot8rXUcYNE2ITrwDvFbIYuF2TbPX3UHm2sCeBlMDIcjKyfX6KZRLuUMlNnSlBS1Ux r44QOCqjaf4F0OfTvVPpLYj2MtcgajUO4BCVTcdZZNfbca+PHVS/oJTaCcJxqPLUCSNb r9jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=N+KH0bFLs52wGl8kzsXXlEDsvOIn0U7dgBgJ6SkG/So=; b=Hh50ULmtOwmNmPsULlBdNskBqCA9Hjp97aBpYzrqUldiktQrWHPge8mYPwSGuWYWTA wcH5P1k9IrHJZs8KODkdO1usNP66yxcMnrvfbWASRwtAA63O0qwd9cTkWe1CoT0+Mu1z 725bv8Phwk2PBbwVtKgUjf5H7pL8FT9r554CrIbc54i4v9mx9besQfg6QNi7maFuI/Km C+vzwby/nNYlfixtpZhGAgkc9Mbv9o+9FRtaxDFaqUth4MjCqG67On2keRkrwjhNuU6q ZXjyq4Qh3qyJh/9k+HUt/nLs5z2Bu5ppb7mbrSqr248jmnga+SQ/I4rE8DA0apYnQJR7 KjtA== X-Gm-Message-State: ACgBeo0rdROc8L5YOrbp4aK7pwocCJIQLlORxS/ubxXjwievTo0Yc/x9 uK8/C0GnVX6Z8f/SuYrJNQJs7ujIqH4sNYayCdG3CA== X-Google-Smtp-Source: AA6agR5JdE5bkesNzzxbwqA+UWtd9va9jrqL6BDhUAQIpLp41G5EDtiAnmNRcVYiAJuIVb7BChOlukChQiI+Dr/naCo= X-Received: by 2002:a25:602:0:b0:6ac:9a9b:f587 with SMTP id 2-20020a250602000000b006ac9a9bf587mr3750619ybg.125.1662572648292; Wed, 07 Sep 2022 10:44:08 -0700 (PDT) MIME-Version: 1.0 References: <20220907173903.2268161-1-elver@google.com> <20220907173903.2268161-2-elver@google.com> In-Reply-To: From: Marco Elver Date: Wed, 7 Sep 2022 19:43:32 +0200 Message-ID: Subject: Re: [PATCH 2/2] objtool, kcsan: Add volatile read/write instrumentation to whitelist To: Boqun Feng Cc: "Paul E. McKenney" , Mark Rutland , Dmitry Vyukov , Alexander Potapenko , kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org, Nathan Chancellor , Nick Desaulniers , llvm@lists.linux.dev Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Sept 2022 at 19:42, Boqun Feng wrote: > > On Wed, Sep 07, 2022 at 07:39:03PM +0200, Marco Elver wrote: > > Adds KCSAN's volatile barrier instrumentation to objtool's uaccess > > Confused. Are things like "__tsan_volatile_read4" considered as > "barrier" for KCSAN? No, it's what's emitted for READ_ONCE() and WRITE_ONCE(). Thanks, -- Marco