[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181121175809.GT12932@dhcp22.suse.cz>
Date: Wed, 21 Nov 2018 18:58:09 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Mike Rapoport <rppt@...ux.ibm.com>
Cc: linux-api@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>, Jan Kara <jack@...e.cz>,
Dan Williams <dan.j.williams@...el.com>,
David Rientjes <rientjes@...gle.com>
Subject: Re: [RFC PATCH 1/3] mm, proc: be more verbose about unstable VMA
flags in /proc/<pid>/smaps
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
Powered by blists - more mailing lists