From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f200.google.com (mail-io0-f200.google.com [209.85.223.200]) by kanga.kvack.org (Postfix) with ESMTP id 2C3C36B000C for ; Tue, 3 Jul 2018 12:20:05 -0400 (EDT) Received: by mail-io0-f200.google.com with SMTP id p17-v6so1993438iob.14 for ; Tue, 03 Jul 2018 09:20:05 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id e42-v6sor537794jak.99.2018.07.03.09.20.04 for (Google Transport Security); Tue, 03 Jul 2018 09:20:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <69eb77f7-c8cc-fdee-b44f-ad7e522b8467@gmail.com> From: Daniel Colascione Date: Tue, 3 Jul 2018 09:20:02 -0700 Message-ID: Subject: Re: [REGRESSION] "Locked" and "Pss" in /proc/*/smaps are the same Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Vlastimil Babka Cc: Thomas Lindroth , Andrew Morton , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm On Tue, Jul 3, 2018 at 12:36 AM, Vlastimil Babka wrote: > +CC > > On 07/01/2018 08:31 PM, Thomas Lindroth wrote: >> While looking around in /proc on my v4.14.52 system I noticed that >> all processes got a lot of "Locked" memory in /proc/*/smaps. A lot >> more memory than a regular user can usually lock with mlock(). >> >> commit 493b0e9d945fa9dfe96be93ae41b4ca4b6fdb317 (v4.14-rc1) seems >> to have changed the behavior of "Locked". Thanks for fixing that. I submitted a patch [1] for this bug and some others a while ago, but the patch didn't make it into the tree because or wasn't split up correctly or something, and I had to do other work. [1] https://marc.info/?l=linux-mm&m=151927723128134&w=2