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 D2129C433EF for ; Tue, 21 Dec 2021 09:23:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236331AbhLUJXl (ORCPT ); Tue, 21 Dec 2021 04:23:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60012 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232251AbhLUJXk (ORCPT ); Tue, 21 Dec 2021 04:23:40 -0500 Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A88CFC061574 for ; Tue, 21 Dec 2021 01:23:39 -0800 (PST) Received: by mail-qk1-x72c.google.com with SMTP id m186so11960207qkb.4 for ; Tue, 21 Dec 2021 01:23:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xzwisqb1Sy2od8aWgP/bz4IaYgTJ8bQBQSdhNAj9vNM=; b=VyLPgc+N3ejMZB5IuZpuMhrPHt40i6UgHuVzvVUlYzns/vLh7SllYTfzOm95Ydu08d bx7Ijb4zr3t69OAIEg9m0V6YlE33teplPktDpkPw0gG63SHbfd16CU+wVWw+Oef1tcku P/vcm1/Ru/jSA5g0tcErfFLo7NpZdN66pUoNO53kYQf3CiY4BMfHPfNhbFjVvTFOKqWp iaGgdXRexxwOQKTIM3+EhOj9fgBa4giaI8mSMwEdsb5MTMgEUJDkb8OulUL+3ClUD/Ub AZVUBHrqVyBimX6Rl6yaNdzGUI1dm7GgJgbXeDKaxqHBSAY0bTYqzWr9wU6738yOmXy5 IWDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xzwisqb1Sy2od8aWgP/bz4IaYgTJ8bQBQSdhNAj9vNM=; b=RI6XN4VweUkMwjxF3XQ+FyOAdyyUt5rYVnZMoeGVkpvnSoNgvXxgRMxdoXfhEcIpC8 IePNudxWX2cGT+NVtLw7UXXkS2PB+qx4Krjxu4dUN5O/TH3YJrBWxnPaI6oP9n5P3LeU l+7TKAkN9X7UszwVMnCtxkXyk1ElsDQJy2Nu9Q4w1mw6fwTK272NhoA7Mxk2KBop8W1N 9QiivtdArpY1wHn4rZJmPETUMXsQiAMrcpr2FRz/hJOhNwYE59pb+bEokyUPvgQHNgad ixLWVnlhBcRQTOxg5JQv4TKLUBaLdciL8zAxlmLpnia+RrRV3TslU7KCXL2R28H7GSY6 BmbQ== X-Gm-Message-State: AOAM532FAVqPQs4sN6Ry+xS6Qw7G3kYjWcDthSWKdjs50HXqJRjYTsvH vYtj3fjdAfKD11wW2B4H9C69AzPohCFVVTALUgcx8w== X-Google-Smtp-Source: ABdhPJwUQwtUA7ETB7iiXK+EgRxi4jixcxQLCwfTNYX/jDe2+vsavoXHf7aXOqIotNdigbbLBx3ZmfbySHD7LauTBvM= X-Received: by 2002:a05:620a:2848:: with SMTP id h8mr1353598qkp.610.1640078618621; Tue, 21 Dec 2021 01:23:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Alexander Potapenko Date: Tue, 21 Dec 2021 10:23:02 +0100 Message-ID: Subject: Re: [PATCH mm v4 16/39] kasan: define KASAN_VMALLOC_INVALID for SW_TAGS To: andrey.konovalov@linux.dev Cc: Marco Elver , Andrew Morton , Andrey Konovalov , Dmitry Vyukov , Andrey Ryabinin , kasan-dev , Linux Memory Management List , Vincenzo Frascino , Catalin Marinas , Will Deacon , Mark Rutland , Linux ARM , Peter Collingbourne , Evgenii Stepanov , LKML , Andrey Konovalov Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 20, 2021 at 11:00 PM wrote: > > From: Andrey Konovalov > > In preparation for adding vmalloc support to SW_TAGS KASAN, > provide a KASAN_VMALLOC_INVALID definition for it. > > HW_TAGS KASAN won't be using this value, as it falls back onto > page_alloc for poisoning freed vmalloc() memory. > > Signed-off-by: Andrey Konovalov Reviewed-by: Alexander Potapenko