Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp6279523rwd; Mon, 19 Jun 2023 05:13:39 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4OJY5vNjWH+rWoNT/X01Tf3lpZxrBozFypjMVHUZY9ZdaieHfM+rWwp/PVIO+LVKEzeco3 X-Received: by 2002:a05:6a20:a129:b0:11a:c623:7849 with SMTP id q41-20020a056a20a12900b0011ac6237849mr648966pzk.48.1687176819335; Mon, 19 Jun 2023 05:13:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687176819; cv=none; d=google.com; s=arc-20160816; b=ybq4y0cn4fIDdkxO9f7Ev6lZaXCEBNubxkQhwyjXDrt+hlIi35HcZapte+SCd9yzvN 604SJpiN1cnouAewDJGvxuHRoU01fnrfmotz/5sGWOx5IszgSb3wvEF6LzkWa8LKW4Wf jL7rYI7U/74DdrYPNFQVk0bW5dMy1SKZ6fWySgYbYqLiPpGd0Va5AhEy/lhuFvVv09uE uQQ7jyuzFurUQlPtBWbJFRb0dBjYSc0G3UIQDZop4N0rO2F+M7GHVwAVPDrgGdRG6kfs hTwWW+Df0q/xbyd7Kj22uiDD13UL8EWHmjEvLl+LjsTS74r1BRG/Fu/YIZaPSlNRKfhA WvHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=FvbuaaSlDBqWb5lPKsIhoBijmFdvxXqOiBhjtzjptTs=; b=ZWl4YiGXaGa6jzRc5v4fddw3GcBBZRWYe34Y/ok4o9Vuoki46dbYqEI0j6KLtC4i0P F+2JUJQXLc6qwIJL8IhJF/BqlkWljA+tfKFDKG5G3n0OEsyGyQ+DUClc4KA6RijrKkxq I8R5C/7hihLLi+yOI7w6inTVDsaKu+Kd0GsOH7ry5yEu+Q2gvI2AWVmOsNqhxe2u18S+ JzUlDoP7DWVXXH0I/6TLgSs4wwXVrvdK+yoPvCuT8U18sVc+UzEo23VcVgG/ERC9dm26 37dBKO2QzTfH1ddxT5cYgGU99iagmPX6bHi3qL49d4sz50mN9f3X36swHbgtDQsI5YBQ M6aA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=GmVrGv8D; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c17-20020a170902d49100b001b02658db01si21131708plg.580.2023.06.19.05.13.15; Mon, 19 Jun 2023 05:13:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=GmVrGv8D; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S231607AbjFSLhA (ORCPT + 99 others); Mon, 19 Jun 2023 07:37:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52792 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229519AbjFSLg7 (ORCPT ); Mon, 19 Jun 2023 07:36:59 -0400 Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29318C9 for ; Mon, 19 Jun 2023 04:36:58 -0700 (PDT) Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2b475b54253so16056251fa.2 for ; Mon, 19 Jun 2023 04:36:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1687174616; x=1689766616; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FvbuaaSlDBqWb5lPKsIhoBijmFdvxXqOiBhjtzjptTs=; b=GmVrGv8DUt0/UIzYHV7LoaYoTMEobq2qs8xsfKhSEH2CDK/YmxFQxL9p1XYI0p36VO 2MX0y1ziSurytO3Z8bAAgI9i86qTcDxjUnqs+ml6t7hnFd8iB+s0IDi5T5RdnzVcLWYC T99IKNnTy27cVR57dOBvSaibI6oLrx9fumpqKLekyoY5lq9Wrt+nzeRz2DFFAjagZ1qB ohFBz/7DXc0jl7cTIYycN5/xNkynU3iAQaBEzd+NeshrxW7JUadykXbpH1y4RszyBZ4H aciTdcct4AupyDpm9ZhL0QQSMEGUvdRKUoFMD4i54tVqY4LsM6s+YLhfl7XTOz9yNOgV 2Whw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687174616; x=1689766616; h=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=FvbuaaSlDBqWb5lPKsIhoBijmFdvxXqOiBhjtzjptTs=; b=VRh9p6/exj0YChggcIofSY9Ptg8QF5anIxDBCDHC2ADc7dGjABlc2XYJJHD0vP7iRl vWy4rGOHIy0xTx0U3eU5oJOgPSjcKf3/rJ/50/amJn8wGVOuUSgW/i6TBVN7iyoTce2u j7v9Q8DdPAus2bfHeCa7I4HzFzZv/ISJnwRP5M7Jee468YwSgYhKS3MY92b2Rr/bRmin NbHG3btVDvknd2mWk4j8bPrhRM9GJ9/4nD1p8fLoor13OnNifLBPFDRBV84f2R97P5l6 HCKXwf/lj6JnTjyS9zKLbJwj5F42K0kqhV9eV9bjmxOLXseOxYmMranIPLs+KCP4I8s3 Mcfg== X-Gm-Message-State: AC+VfDyexTqrI1YvzEEfCiM7829ffytBNkusvgi+rr4amqG4At2Yu7AZ HS93A1+xy/48axC2L87ReKSbRGuA5aRH/r/hzrdH0w== X-Received: by 2002:a19:5f07:0:b0:4dd:9f86:859d with SMTP id t7-20020a195f07000000b004dd9f86859dmr5082021lfb.13.1687174616231; Mon, 19 Jun 2023 04:36:56 -0700 (PDT) MIME-Version: 1.0 References: <20230619101224.22978-1-chanho.min@lge.com> In-Reply-To: From: Marco Elver Date: Mon, 19 Jun 2023 13:36:19 +0200 Message-ID: Subject: Re: [PATCH] kasan: fix mention for KASAN_HW_TAGS To: Dmitry Vyukov Cc: Chanho Min , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Vincenzo Frascino , kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, gunho.lee@lge.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 19 Jun 2023 at 12:15, Dmitry Vyukov wrote: > On Mon, 19 Jun 2023 at 12:12, Chanho Min wrote: > > > > This patch removes description of the KASAN_HW_TAGS's memory consumption. > > KASAN_HW_TAGS does not set 1/32nd shadow memory. > > The hardware still allocates/uses shadow in MTE. > Though, it may be 1/16-th, not sure. I think the point is that it depends on the hardware implementation of MTE. There are a range of possibilities, but enabling KASAN_HW_TAGS doesn't consume any extra memory for tags itself if the hardware has to enable MTE and provision tag space via firmware to begin with. > > Signed-off-by: Chanho Min I think you just have to be a bit clearer in the commit description, just briefly mentioning how/where the tag space is allocated in hardware that do support MTE. Then removing this line is probably fair, if KASAN_HW_TAGS isn't the direct reason for tag memory being allocated.