Received: by 10.223.185.116 with SMTP id b49csp723948wrg; Wed, 14 Feb 2018 06:07:28 -0800 (PST) X-Google-Smtp-Source: AH8x225WrIgOUg4jgAOWQdr2RA8aXBUdve02MXPSZ4thzrE/tcEG/Wq0v3NXBUZ49SRyrPe7P2aU X-Received: by 2002:a17:902:9044:: with SMTP id w4-v6mr4650201plz.354.1518617247996; Wed, 14 Feb 2018 06:07:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518617247; cv=none; d=google.com; s=arc-20160816; b=pfWQqgw52qDpM0/4rMx7pXVgU3BcGPX+8WRIkU9LATLRaeqyEMM3SpD/esuLw27fEO UUSuIMiZZToOu/op4BTunmQXsAAt1Dx5JVC2GJ2avkxVsG7kiwVhC+5G4/r5isYlxDg1 /b6HVKoP5Fy/oEYWrRxJz+tLAxfTuay0jjhpvQriUVAs6uUqlf5tQIgwrr0kISUsR8Gn E6gOMxXkM+CbqFA5k1sbjOt3XipOBhBTsoLPiaPFKqYqiNKmx95sYv605ahUoYmQchfn h0XD+YLhIAKLsLyb69tLVRZlV0EXq4Aa+c/XX0VQlkmsIiliKTN4uIzkRV0at6DL/aUt 0tHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=5Ud2uY0+hg4KXlJkIm0NEXX0fMzSNTrmsY/tsv5seRo=; b=B1pKLeoJyg/kgS9DDQKpaZvO+Uqm9OpPsVFBEbJQmC91vSMSeuUsL2n/UpRQmcIWKM fBaKRojDoaaIXdw/2y3dCDHi22g4Vwuoyl+80FpztenPeU1k8WL/AILV4cToPtP+cusm +Kz9aW85u4RfO6OMkqWty2qihcMnkNiQ/+OTmW0irmtcfUlj4n64eUHAbpzgSS3ZQh0x sU4L59MwNHjxAga5GcKlf9/LUEYsQXN7MianBxq7D8aufHueT/yF7yvbyha7ngVHYIPv 8zUO7HAmjR9IHaEvxyb8R76PEPrpy6ii1lcRN67/PK+bXGA7D0Xg3cosdVoFYbqb4lVv V6Fw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=deUtoxs9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o15-v6si1270874pli.460.2018.02.14.06.07.12; Wed, 14 Feb 2018 06:07:27 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@shutemov-name.20150623.gappssmtp.com header.s=20150623 header.b=deUtoxs9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030686AbeBNOFW (ORCPT + 99 others); Wed, 14 Feb 2018 09:05:22 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:35883 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030450AbeBNOFV (ORCPT ); Wed, 14 Feb 2018 09:05:21 -0500 Received: by mail-wm0-f50.google.com with SMTP id f3so22214424wmc.1 for ; Wed, 14 Feb 2018 06:05:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shutemov-name.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=5Ud2uY0+hg4KXlJkIm0NEXX0fMzSNTrmsY/tsv5seRo=; b=deUtoxs9p2z4tS0onVF+lS5O7a0YVGuKiZpzi5gboNoYJKjnqrW/WWg9LaY1saMOhC PuC2//3ZXsrsvAr0zANue1mWFvkFcKF/eS4IUVFBAu51yNjTnH42QTnGLhDcs7NuV5bU XNN12l6kxLc+PAKooeuZ/k8DyElHYFU77twfgyzOsBsu6xLv0PgJpNTWFjOhsv/H0ETZ Ax13WWd5x6VEAeeLu94QFVvLSncu68y/D/lQ9TWd3ed8yF6qPUNQFxArwQPazSBs+wks GqOwc2M9RftzLg2DRGYUbI05FyGInX+K237F67Ej2bp3ETu3bX9Q3X95H4SoPCnoCQwA v43w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=5Ud2uY0+hg4KXlJkIm0NEXX0fMzSNTrmsY/tsv5seRo=; b=FOpUtL4HbUf5RwvThLJVLwbPdd8KdJuZqcnL7FOUGLe3GLXsKu2PezNux2W5PwIxod h+2eRwPlvJUzSzWmG1aZIOkcZvpMX+I83JetkJm9Ewmp6vk5CYONhYbt0eml3YKqO7XD fv2COB0aYFf21fWRFruIlb+hML08kxzAPj/WZCrebGA87+cDljKjHmK/hxMQCB9x37AC RoOeZkitPUvuxqg+QykkXV7Kjj1xFkPGoCBNaSKuRqIDs0zJzo6z75hGuhQk6p8E3ujn fh4+D6/gnmWSn/zWAk1pJFGbIhjM/CJ4ZuLE7czt0alh8FfA7w0asrLoXfyaPXlQpJEV dr9Q== X-Gm-Message-State: APf1xPAKBbiFBkj+bctFJQlcunlrkOfakqGNw03+aX8X4v5zNZn2ND42 c2dC5ONMdvcVIBmQ1VjUqLb9fQ== X-Received: by 10.80.189.139 with SMTP id y11mr7065486edh.122.1518617118859; Wed, 14 Feb 2018 06:05:18 -0800 (PST) Received: from node.shutemov.name ([178.121.192.223]) by smtp.gmail.com with ESMTPSA id p6sm8329351edb.62.2018.02.14.06.05.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Feb 2018 06:05:18 -0800 (PST) Received: by node.shutemov.name (Postfix, from userid 1000) id 225B6648D520; Wed, 14 Feb 2018 17:05:17 +0300 (+03) Date: Wed, 14 Feb 2018 17:05:17 +0300 From: "Kirill A. Shutemov" To: Matthew Wilcox Cc: Daniel Micay , Jann Horn , linux-mm@kvack.org, Kernel Hardening , kernel list , "Kirill A. Shutemov" Subject: Re: [RFC] Limit mappings to ten per page per process Message-ID: <20180214140517.ipgxvskdy7bwl7up@node.shutemov.name> References: <20180208185648.GB9524@bombadil.infradead.org> <20180208194235.GA3424@bombadil.infradead.org> <20180208202100.GB3424@bombadil.infradead.org> <20180208213743.GC3424@bombadil.infradead.org> <20180209042609.wi6zho24wmmdkg6i@node.shutemov.name> <20180214135141.GA16215@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180214135141.GA16215@bombadil.infradead.org> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 14, 2018 at 05:51:41AM -0800, Matthew Wilcox wrote: > On Fri, Feb 09, 2018 at 07:26:09AM +0300, Kirill A. Shutemov wrote: > > On Thu, Feb 08, 2018 at 01:37:43PM -0800, Matthew Wilcox wrote: > > > On Thu, Feb 08, 2018 at 12:21:00PM -0800, Matthew Wilcox wrote: > > > > Now that I think about it, though, perhaps the simplest solution is not > > > > to worry about checking whether _mapcount has saturated, and instead when > > > > adding a new mmap, check whether this task already has it mapped 10 times. > > > > If so, refuse the mapping. > > > > > > That turns out to be quite easy. Comments on this approach? > > > > This *may* break some remap_file_pages() users. > > We have some?! ;-) I can't prove otherwise :) > I don't understand the use case where they want to map the same page of > a file multiple times into the same process. I mean, yes, of course, > they might ask for it, but I don't understand why they would. Do you > have any insight here? Some form of data deduplication? Like having repeating chunks stored once on presistent storage and page cache, but put into memory in "uncompressed" form. It's not limited to remap_file_pages(). Plain mmap() can be used for this too. -- Kirill A. Shutemov