Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2808386pxb; Tue, 12 Oct 2021 14:01:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZHcixP9cNZm38uE+RTDDQCTODKj6kySZjAUTqFWrw3WRq7G1Nhjl8163FT1IqKFSQjW7p X-Received: by 2002:a17:90a:8912:: with SMTP id u18mr8417361pjn.69.1634072469002; Tue, 12 Oct 2021 14:01:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634072468; cv=none; d=google.com; s=arc-20160816; b=ap7ImHOfXuXx5W46BhRwv2csIDggnskPgXSt9gyPxR8ZC01N1nZ7Tm9KGYarFE+PCo AyuVT73aYqdcW70ELmJx+wlDOIGcoXYTP+mqFNbsROOHM1kUZChK9v/Xqz+WszR53S+a AwB+nespPLuUVM2TMZz/QGy0exlSEuLSstbL1yECQoQxUMyvnHN/gyxJpK5QRXbOQggy cpMfPsQP2HuuOSDyWteonKnSKBgkWkADCRZamSPezEv4r21kdq2byKG80oxkUK7V4zcX WtbaSWqjpYtu14rWxY5CODSrQvLZ75RxxgTF2kc0oit3G3dpNsPCnI+QpPpTja6t5mvd wxSA== 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=/FM46KTu0fl8cFqAAvga2i5cJZtMLiEZlRnNB5JincE=; b=Vy1Bp5sRh9ttMhvwRtccyTSZbu0vpA7SI8VyGvxhat3mon8HiXsbrL24Tr61iEScky 6vXU44hYMBvGgbNoxw+j6raovO8OyhRAqkaAfmK49yUREXnzXyhSFluu68scnglFCiCK HFUuytxqhwQxCVtyLehYCE4oCljx3xJ7cJi+sn6xJd7w2bu61nK3uWjefEB1u3EF5Vwp YV2HxXvla3hfWZOqIsomoWCaI4rISCyIeOV6JWINj7dpRJRSrmuLyT0UBbTuNrZ3y/x7 RgouHqVZsL2UyV6uP6qyTiU6GA4sVrzR1a/Wurf/oHdiv1/1GBgVgX/ewwKGXKEnUbYt ktrA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=Wh5JIU1b; 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 x22si16405029pgj.320.2021.10.12.14.00.55; Tue, 12 Oct 2021 14:01:08 -0700 (PDT) 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=20210112 header.b=Wh5JIU1b; 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 S233224AbhJLVB4 (ORCPT + 99 others); Tue, 12 Oct 2021 17:01:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37244 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232860AbhJLVB4 (ORCPT ); Tue, 12 Oct 2021 17:01:56 -0400 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EFFC8C061570 for ; Tue, 12 Oct 2021 13:59:53 -0700 (PDT) Received: by mail-yb1-xb2a.google.com with SMTP id r1so1349360ybo.10 for ; Tue, 12 Oct 2021 13:59:53 -0700 (PDT) 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=/FM46KTu0fl8cFqAAvga2i5cJZtMLiEZlRnNB5JincE=; b=Wh5JIU1bBIUxbXwo4tp7JMR0cu8a0lDIJia6OgZEgEx72jrSvyydXbNV/+rad2r42T hah7gUOQnYJDVsXVLrHL2P7RzyBcSKTODkVABWXWtjZmFMWcW5EmtRQ8vpl4Gc+ae7Ff pRvMzQJ1iLMkito1wcmawmuKld81XX+yckDiInbDA897OlXQwkXl8+HD6s6+R/r4omMi vO7yrbR9yqS+gW2kbDXz1X/LoLPSdojSS5UTz6i7glen7IZbhAcdFLm3F3TNrEYeJKx/ vd2K8RTUnROyejv3lCt/DagoM5MqcIta4pck8EI7wV/sDdUN0r7jbA5aCI2GezvUwclT kO1w== 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=/FM46KTu0fl8cFqAAvga2i5cJZtMLiEZlRnNB5JincE=; b=qFyza2TMTOdWTfk7dToivbucVvKzWQQA80MO+Qyq6VjDAUUptnQPbHDu/0840lpBzW OM8237iAsvMNTqCEkVkw5hzchESG+l31T5F8XVGMcHyG/P9pcqxVhABKVrrduYqhmCwO o7BJ3XRiEZ+rVmqSUYcBf+nES5ByM9OlGZDNY0muspKrvNWgOsZrM2+2CJk7nj5Y2IU2 1qb632XcxngU/O6e4dF9dt7N4s8Xf2qT4uEhI0a6k5+IOhk3PlxgsT1CwVNl9NQTDu6N e/BDca2r07rNU8tm0nUAYN9oi3rA+GgB2k0N9/y38UZvzTrIwqznnT/LrKx47qqw+ywu byHQ== X-Gm-Message-State: AOAM530+0hiL2TEoHfYzgqTAGw/NbuCmeM7Wb/Pg3dipTGbUQ/DinTDF SHn+OUCa1GRjWUZfqyM1oeqdatjRTJ/6Ldq/bHDcmQ== X-Received: by 2002:a05:6902:120e:: with SMTP id s14mr34368157ybu.161.1634072392293; Tue, 12 Oct 2021 13:59:52 -0700 (PDT) MIME-Version: 1.0 References: <202110071111.DF87B4EE3@keescook> <202110081344.FE6A7A82@keescook> In-Reply-To: From: Suren Baghdasaryan Date: Tue, 12 Oct 2021 13:59:40 -0700 Message-ID: Subject: Re: [PATCH v10 3/3] mm: add anonymous vma name refcounting To: Johannes Weiner Cc: Michal Hocko , Kees Cook , Pavel Machek , Rasmus Villemoes , David Hildenbrand , John Hubbard , Andrew Morton , Colin Cross , Sumit Semwal , Dave Hansen , Matthew Wilcox , "Kirill A . Shutemov" , Vlastimil Babka , Jonathan Corbet , Al Viro , Randy Dunlap , Kalesh Singh , Peter Xu , rppt@kernel.org, Peter Zijlstra , Catalin Marinas , vincenzo.frascino@arm.com, =?UTF-8?B?Q2hpbndlbiBDaGFuZyAo5by16Yym5paHKQ==?= , Axel Rasmussen , Andrea Arcangeli , Jann Horn , apopple@nvidia.com, Yu Zhao , Will Deacon , fenghua.yu@intel.com, thunder.leizhen@huawei.com, Hugh Dickins , feng.tang@intel.com, Jason Gunthorpe , Roman Gushchin , Thomas Gleixner , krisman@collabora.com, Chris Hyser , Peter Collingbourne , "Eric W. Biederman" , Jens Axboe , legion@kernel.org, Rolf Eike Beer , Cyrill Gorcunov , Muchun Song , Viresh Kumar , Thomas Cedeno , sashal@kernel.org, cxfcosmos@gmail.com, LKML , linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm , kernel-team , Tim Murray Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 12, 2021 at 1:41 PM Johannes Weiner wrote: > > On Tue, Oct 12, 2021 at 11:52:42AM -0700, Suren Baghdasaryan wrote: > > On Tue, Oct 12, 2021 at 11:26 AM Johannes Weiner wrote: > > > > > > On Mon, Oct 11, 2021 at 10:36:24PM -0700, Suren Baghdasaryan wrote: > > > > On Mon, Oct 11, 2021 at 8:00 PM Johannes Weiner wrote: > > > > > > > > > > On Mon, Oct 11, 2021 at 06:20:25PM -0700, Suren Baghdasaryan wrote: > > > > > > On Mon, Oct 11, 2021 at 6:18 PM Suren Baghdasaryan wrote: > > > > > > > > > > > > > > On Mon, Oct 11, 2021 at 1:36 AM Michal Hocko wrote: > > > > > > > > > > > > > > > > On Fri 08-10-21 13:58:01, Kees Cook wrote: > > > > > > > > > - Strings for "anon" specifically have no required format (this is good) > > > > > > > > > it's informational like the task_struct::comm and can (roughly) > > > > > > > > > anything. There's no naming convention for memfds, AF_UNIX, etc. Why > > > > > > > > > is one needed here? That seems like a completely unreasonable > > > > > > > > > requirement. > > > > > > > > > > > > > > > > I might be misreading the justification for the feature. Patch 2 is > > > > > > > > talking about tools that need to understand memeory usage to make > > > > > > > > further actions. Also Suren was suggesting "numbering convetion" as an > > > > > > > > argument against. > > > > > > > > > > > > > > > > So can we get a clear example how is this being used actually? If this > > > > > > > > is just to be used to debug by humans than I can see an argument for > > > > > > > > human readable form. If this is, however, meant to be used by tools to > > > > > > > > make some actions then the argument for strings is much weaker. > > > > > > > > > > > > > > The simplest usecase is when we notice that a process consumes more > > > > > > > memory than usual and we do "cat /proc/$(pidof my_process)/maps" to > > > > > > > check which area is contributing to this growth. The names we assign > > > > > > > to anonymous areas are descriptive enough for a developer to get an > > > > > > > idea where the increased consumption is coming from and how to proceed > > > > > > > with their investigation. > > > > > > > There are of course cases when tools are involved, but the end-user is > > > > > > > always a human and the final report should contain easily > > > > > > > understandable data. > > > > > > > > > > > > > > IIUC, the main argument here is whether the userspace can provide > > > > > > > tools to perform the translations between ids and names, with the > > > > > > > kernel accepting and reporting ids instead of strings. Technically > > > > > > > it's possible, but to be practical that conversion should be fast > > > > > > > because we will need to make name->id conversion potentially for each > > > > > > > mmap. On the consumer side the performance is not as critical, but the > > > > > > > fact that instead of dumping /proc/$pid/maps we will have to parse the > > > > > > > file, do id->name conversion and replace all [anon:id] with > > > > > > > [anon:name] would be an issue when we do that in bulk, for example > > > > > > > when collecting system-wide data for a bugreport. > > > > > > > > > > Is that something you need to do client-side? Or could the bug tool > > > > > upload the userspace-maintained name:ids database alongside the > > > > > /proc/pid/maps dump for external processing? > > > > > > > > You can generate a bugreport and analyze it locally or submit it as an > > > > attachment to a bug for further analyzes. > > > > Sure, we can attach the id->name conversion table to the bugreport but > > > > either way, some tool would have to post-process it to resolve the > > > > ids. If we are not analyzing the results immediately then that step > > > > can be postponed and I think that's what you mean? If so, then yes, > > > > that is correct. > > > > > > Right, somebody needs to do it at some point, but I suppose it's less > > > of a problem if a developer machine does it than a mobile device. > > > > True, and that's why I mentioned that it's not as critical as the > > efficiency at mmap() time. In any case, if we could avoid translations > > at all that would be ideal. > > > > > > > > One advantage of an ID over a string - besides not having to maintain > > > a deduplicating arbitrary string storage in the kernel - is that we > > > may be able to auto-assign unique IDs to VMAs in the kernel, in a way > > > that we could not with strings. You'd still have to do IPC calls to > > > write new name mappings into your db, but you wouldn't have to do the > > > prctl() to assign stuff in the kernel at all. > > > > You still have to retrieve that tag from the kernel to record it in > > your db, so this would still require some syscall, no? > > Don't you have to do this with the string setting interface as well? > How do you know the vma address to pass into the prctl()? Is this > somehow coordinated with the mmap()? Sure. The sequence is: ptr = mmap(NULL, size, ...); prctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, ptr, size, name); > > > > (We'd have to think of a solution of how IDs work with vma merging and > > > splitting, but I think to a certain degree that's policy and we should > > > be able to find something workable - a MAP_ID flag, using anon_vma as > > > identity, assigning IDs at mmap time and do merges only for protection > > > changes etc. etc.) > > > > Overall, I think keeping the kernel out of this and letting it treat > > this tag as a cookie which only userspace cares about is simpler. > > Unless you see other uses where kernel's involvement is needed. > > It depends on what you consider keeping the kernel out of it. A small > extension to assign unique IDs to mappings automatically in an > intuitive way (with a compat option to disable) is a much smaller ABI > commitment than a prctl()-controlled string storage. I'm not saying it's hard or complex. I just don't see the advantage of generating these IDs in the kernel vs passing them from userspace. Maybe I'm missing some usecase? > When I say policy on how to assign the ID, I didn't mean that it > should be a free for all. Rather that we should pick one reasonable > way to do it, comparable to picking the parameters for how long the > stored strings could be, which characters to allow etc.