Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp853502pxu; Mon, 23 Nov 2020 05:58:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJy2CKXYYr0ybtrtNeRoe8Mu0Pn8UyyfXpdHJj+pVahZkBJi1MspXzAY3Gxci4dQ6IU+KaQU X-Received: by 2002:a17:906:f10e:: with SMTP id gv14mr43364724ejb.346.1606139880275; Mon, 23 Nov 2020 05:58:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606139880; cv=none; d=google.com; s=arc-20160816; b=Anqrjj5ifxslqrZn5bTMe97HvVPWg5yqbvpA0Z+IkdD6dI9z9DxMZ23MO82xfcZsCJ 1X2Ty8hzPrXhTESv6yzZGVuJNDAUH1alNJsDOZRVOjeUNxlNBs0CTUupA/lRT2VVEsRi ODVW1uUrDbsj9hYWAQ+Gcde6F5AMslhhvER9qjeB8oYOcP7Wg3cKr9Wgx96kbqyDl9tC Y6bZViHXPjWjU13ah3OAE10BMup6VfK8eonycX9yH2V2cUVMngIw+FQnsLExoaQ8opoZ e+WrPJp2V3OKT1OYYkd5e+9Z8FrbZI3Zy9DcMU+UMISi1SkQWGQjxuDhxN4y3Nmrg/6N SPsA== 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=088zmG11B7ENQeStfIt/hKr66YTpt35vQc34h9N/mec=; b=rJd6BEG6v9Yr9w13QhN+Symo3FnCaBGDRD7R7kbBx54Mhl7ERaWwJ+qWl0nNH6jtMo h23XMq1AD52WzGdsUiSXTYEYrDv3r6fBEcSQ4W/KEAieGwvyjexrgX6G90uVQb/Rgt2u bf4Rpgv68p6z7Mkb2Hj7JyYEaoaEhlNNJVyUENNXtmXWMGQ9itvHf+Gh7xC1J2US5XSB BbKxJcQaKKQWij7V7ABr3YbY12Znp7gpwic/wWMmSHVuMUvz/XLl5w1I1P57kxLKiuBz wU/LPdDwK3E6WvgpOdWPRCzWPrnjPL/Vvb3R8UwMYtsAU3wjEWyehC+syFRzA1QgJR2v JzvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=WwhwzWGg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id i5si6369634edx.188.2020.11.23.05.57.37; Mon, 23 Nov 2020 05:58:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=WwhwzWGg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S2388766AbgKWNxB (ORCPT + 99 others); Mon, 23 Nov 2020 08:53:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40372 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388750AbgKWNw7 (ORCPT ); Mon, 23 Nov 2020 08:52:59 -0500 Received: from mail-pg1-x541.google.com (mail-pg1-x541.google.com [IPv6:2607:f8b0:4864:20::541]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 17590C0613CF for ; Mon, 23 Nov 2020 05:52:56 -0800 (PST) Received: by mail-pg1-x541.google.com with SMTP id l17so3870558pgk.1 for ; Mon, 23 Nov 2020 05:52:56 -0800 (PST) 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=088zmG11B7ENQeStfIt/hKr66YTpt35vQc34h9N/mec=; b=WwhwzWGgg7krqxKQSWo7qxirBtmz/vdt/6j2DSW4AJ7H0uqC3m0kiJkpBJUucnhIRU regOTZnXOw2Mi23u2xxBoyTAQh/+fHvAJiccNvPdxWN9U1cHeo5sE6tGyzX0cIJPLlaY w+fAPAny5FGyPfO2+0RttYdgJ/tRMrSPdYmX/bNX94ViHoyZGhRhVEIY+W8zmX6IGNA8 nYevFmxgPTO18WEhkQw1uKz+URUyhtoqWU862+CeihUSza4nYw9m5qwhbWsJX9A2o3vA ZgvgnUnLQMI93t7IHi6NpCMu3KZnsu+UZObEw5s6dTmcEThWCXXZcWNZJ5cGrp5dTKMq 9EKQ== 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=088zmG11B7ENQeStfIt/hKr66YTpt35vQc34h9N/mec=; b=VFOcVxPGdm/ztKMp7RNA5I80Jh7Vked5/vb99aY4Xjen5794XVs3vAooEYJkgDaFYp lewuQ9eADzcqhn0eO2U5ziN/KYQzOGMBesdtWjHQWSDQ+3uGVPGgkYoQ9Iu55PRlcTW1 g6Xe340t/yp7mY8R1GaT7gYRr1fsQK5MnQifaPJdaT8A68qe24H6dlaFBu3wld2T5MTD 84jCOsnk7OGr3TjKLu+qJHkpwZv8oHEwmOYrUPDLNDXkw8Xbd3zLs4auTp3EfrERH4nI 2Sh42XKZkje0KjvjYWUvyUoRuxo0XU3jvffD/PN/HhqO8YDs/d4OXiMgAuE2NjXxW/GW HDyQ== X-Gm-Message-State: AOAM530QtGzTh8pm93LuBZu5HmJblWy5IQ6/EfHfxy3BxlVfUq8ZqS3j 4eBemkn6KvJRj07XidhZ8mLdB7Oc1LzAtmWPY/F4+A== X-Received: by 2002:a63:f20:: with SMTP id e32mr27452713pgl.130.1606139575373; Mon, 23 Nov 2020 05:52:55 -0800 (PST) MIME-Version: 1.0 References: <6f0a1e72783ddac000ac08e7315b1d7c0ca4ec51.1605305978.git.andreyknvl@google.com> In-Reply-To: From: Andrey Konovalov Date: Mon, 23 Nov 2020 14:52:44 +0100 Message-ID: Subject: Re: [PATCH mm v3 18/19] kasan, mm: allow cache merging with no metadata To: Dmitry Vyukov Cc: Andrew Morton , Catalin Marinas , Will Deacon , Vincenzo Frascino , Andrey Ryabinin , Alexander Potapenko , Marco Elver , Evgenii Stepanov , Branislav Rankov , Kevin Brodsky , kasan-dev , Linux ARM , Linux-MM , LKML Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 17, 2020 at 2:25 PM Dmitry Vyukov wrote: > > On Fri, Nov 13, 2020 at 11:20 PM Andrey Konovalov wrote: > > > > The reason cache merging is disabled with KASAN is because KASAN puts its > > metadata right after the allocated object. When the merged caches have > > slightly different sizes, the metadata ends up in different places, which > > KASAN doesn't support. > > > > It might be possible to adjust the metadata allocation algorithm and make > > it friendly to the cache merging code. Instead this change takes a simpler > > approach and allows merging caches when no metadata is present. Which is > > the case for hardware tag-based KASAN with kasan.mode=prod. > > > > Co-developed-by: Vincenzo Frascino > > Signed-off-by: Vincenzo Frascino > > Signed-off-by: Andrey Konovalov > > Link: https://linux-review.googlesource.com/id/Ia114847dfb2244f297d2cb82d592bf6a07455dba > > Somehow gerrit contains an old version... so I was going to > independently propose what Marco already proposed as simplification... > until I looked at the patch in the email :) Ah, this is because I couldn't push next/mm-based changes into Gerrit without manually adding tags to all of the yet-out-of-tree patches. So the Gerrit doesn't have the last version of the patchset. > Reviewed-by: Dmitry Vyukov Thanks!