Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2412862imu; Wed, 21 Nov 2018 11:13:13 -0800 (PST) X-Google-Smtp-Source: AFSGD/WaBbXzJfc45XfY7AJVL+ekQDl9W2402IDxlRAOI3rQKFxtmpw6Xpr9DUhgQCrCVA7f/XVD X-Received: by 2002:a17:902:a81:: with SMTP id 1-v6mr8111410plp.20.1542827593444; Wed, 21 Nov 2018 11:13:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542827593; cv=none; d=google.com; s=arc-20160816; b=Zqt5X5ZB3WX7zXVOOMd5vib+145hsyX4r7vpZS2qutbHEy55lhy98R2fidXheiK1Yp HjVqeJalaj+hMCxDglMZnhhW8fSjr9UkJXwoKD2/sqE9bGk2fvuvdJ/CigVS4/MuCxLB yrU0XXg3NBRuKXWpufio77Ikvzfi0u0Jpnrwj6xigsRaQrvRx5bDkQSIynxoZUiaaUre 7GRmRpDZHmjyhUjGL2XUuqSU/jODhQwGCI+sAnZEZ8JbEivfQ/KxyfkSWfgNmJaQULY9 LIp5GsThaFNwI29EXsbd3RDWlP69MYIqnbMXet3MBCskeusLykquBeTWIUnTku5IODWb rLVA== 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; bh=YfcxihBy8Rn5sr2g3oziAPmmZgpaptbAQnEjZqU38pE=; b=ZDh27C+60GtQxpxdpS3KyP6dyC+eGjYTT2kRhBpNPJdsess7fwTwC2mgMTxaNeYFOM Gn8tcX00X62SHyBlaWhLw5Xc1q8ByUXlJARQdwBaNdCkTkeXjuoYNE6R5m3O2GHSj7lx UXTS+srjs4XlWmnyfV2rws+Ix0oJY2Rj+9Hp5qRwkEEY05g0qd9+Vt7D2c29IB6eAETc cAFergz7nxYLypwic1Hv39frQmP/Wsj8Qw7lTwqQfmV4FWq5FO9YEo7wWl6fCQVgmhDJ T4P5QSpltNX7m4r9zQQ1hyMkYyvwg4SrdCrKlIWYD37nfh+xVK3VGhWbd+IiLbn4izjz etZQ== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 20si6066589pgt.469.2018.11.21.11.12.58; Wed, 21 Nov 2018 11:13:13 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732797AbeKVEde (ORCPT + 99 others); Wed, 21 Nov 2018 23:33:34 -0500 Received: from mx2.suse.de ([195.135.220.15]:51708 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731412AbeKVEde (ORCPT ); Wed, 21 Nov 2018 23:33:34 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 381F6ACB8; Wed, 21 Nov 2018 17:58:10 +0000 (UTC) Date: Wed, 21 Nov 2018 18:58:09 +0100 From: Michal Hocko To: Mike Rapoport Cc: linux-api@vger.kernel.org, Andrew Morton , Alexey Dobriyan , linux-mm@kvack.org, LKML , Jan Kara , Dan Williams , David Rientjes Subject: Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA flags in /proc//smaps Message-ID: <20181121175809.GT12932@dhcp22.suse.cz> References: <20181120103515.25280-1-mhocko@kernel.org> <20181120103515.25280-2-mhocko@kernel.org> <20181121175427.GB5704@rapoport-lnx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181121175427.GB5704@rapoport-lnx> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 21-11-18 18:54:28, Mike Rapoport wrote: > On Tue, Nov 20, 2018 at 11:35:13AM +0100, Michal Hocko wrote: [...] > > diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt > > index 12a5e6e693b6..b1fda309f067 100644 > > --- a/Documentation/filesystems/proc.txt > > +++ b/Documentation/filesystems/proc.txt > > @@ -496,7 +496,9 @@ flags associated with the particular virtual memory area in two letter encoded > > > > Note that there is no guarantee that every flag and associated mnemonic will > > be present in all further kernel releases. Things get changed, the flags may > > -be vanished or the reverse -- new added. > > +be vanished or the reverse -- new added. Interpretatation of their meaning > > +might change in future as well. So each consumnent of these flags have to > > consumer? has fixed. Thanks! -- Michal Hocko SUSE Labs