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 41E7EEB64D8 for ; Tue, 20 Jun 2023 11:45:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232783AbjFTLp6 (ORCPT ); Tue, 20 Jun 2023 07:45:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232774AbjFTLpp (ORCPT ); Tue, 20 Jun 2023 07:45:45 -0400 Received: from mail-oo1-xc2d.google.com (mail-oo1-xc2d.google.com [IPv6:2607:f8b0:4864:20::c2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EFC56198B; Tue, 20 Jun 2023 04:45:36 -0700 (PDT) Received: by mail-oo1-xc2d.google.com with SMTP id 006d021491bc7-55b3a245359so3096313eaf.2; Tue, 20 Jun 2023 04:45:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687261536; x=1689853536; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=tJCMKaRS9iIUjy75SMVgQ9VDcAREfFkBluEAU4z9ags=; b=JafGBlk8XfHKEBCbR5tqF5YOtAo+NrGzEussgveHGWOlu8GHvnJB64cbGERaeyJGO3 m9yZ5SotMdegV+GuJJ89oQXjiQLb4KVJHDnoaskf4Cpsm4vW7HsDeFhgzZaL6ttHTaMK 1DPNgnwedQN+wGECrc3w75vbDa37J4OmNHdwRclNP+ZTxYCY//GBZ8BUKse5bA9fhH7Y F3xjOPm2JdBCfgaoYhv1CMhTAEcGrA/zM25EIjnGGCSrqxyvkxOc3Rmw6UIewS+moM48 D/lZWaQ7ulPMq3zBD6WbFN4k33uOlSyAH+Cyd3Y5YaZ395q6VVXIQ9TNeNiLt2IgjBqt BoZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687261536; x=1689853536; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=tJCMKaRS9iIUjy75SMVgQ9VDcAREfFkBluEAU4z9ags=; b=aNafFtjnjJESOCl0xmA/c4L97Dne12gkCll6wwM/XfpnooksIfmsBPHMKkDGL3DmAM nDEukj4KNMhD7tteAwzGDMQlDPnU0mODdSfZd4V65UxXVhTgk7RnbAVeyPJ9i07wx28c F4qBGPYdbjwva26znaqNzYKBrE/+FkvV5/O8/jdnBqv+BDODEpqkfO7/5rT7VHnZATfU 2pX7lLRtDadYUjz6SMechNjrea3S1KnkKPfQkbkIPWBJaEURvFPJXblfhG9LODVgrZqV JrWMW6IhzoBmQnFc5Hb6b/sbM1YU/P9alKNFoSAwgjSlu9/uZbc/vWhslEZuoSUm28Ms bytQ== X-Gm-Message-State: AC+VfDxH4j52uFzd/3IYLidIVYpsq/udEm4hi2ZmkVkeJ1GbWhR4WQBe MpLk8HuRnLblyCR/4u1RzDKOZg3WUHdR3pf8nAQ= X-Google-Smtp-Source: ACHHUZ54uF7mepaUweD5UBJo2z3ZyfBJ1SnIHZ/Wn3QYsgoqkmZdln9JMYd8qBzKPB6APDZFn1NEazVjfaI7UfPLMlY= X-Received: by 2002:a05:6808:2110:b0:39e:ce9d:1a92 with SMTP id r16-20020a056808211000b0039ece9d1a92mr7992873oiw.4.1687261536152; Tue, 20 Jun 2023 04:45:36 -0700 (PDT) MIME-Version: 1.0 References: <20230614095158.1133673-1-elver@google.com> In-Reply-To: From: Andrey Konovalov Date: Tue, 20 Jun 2023 13:45:25 +0200 Message-ID: Subject: Re: [PATCH] kasan: add support for kasan.fault=panic_on_write To: Marco Elver Cc: Andrew Morton , Alexander Potapenko , Dmitry Vyukov , Taras Madan , Aleksandr Nogikh , Andrey Ryabinin , Vincenzo Frascino , Jonathan Corbet , kasan-dev@googlegroups.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Catalin Marinas Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 20, 2023 at 1:33=E2=80=AFPM Marco Elver wrot= e: > > > On a related note, it looks like we have a typo in KASAN > > documentation: it states that asymm mode detects reads synchronously, > > and writes - asynchronously. Should be the reverse. > > This says the documentation is correct, and it's actually called for > writes: https://docs.kernel.org/arm64/memory-tagging-extension.html#tag-c= heck-faults > > Who is right? Ah, right. I did a quick google to check when I was writing the response and found this: https://lwn.net/Articles/882963/. But looks like that cover letter is wrong and the documentation is right. I wonder what the point of the asymmetric mode is then. So the current code that you have should work perfectly. The only change I'd like to see is in the documentation. Thanks!