[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140822134628.5df9cda87d744e35d794b5c2@linux-foundation.org>
Date: Fri, 22 Aug 2014 13:46:28 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Cyrill Gorcunov <gorcunov@...il.com>
Cc: linux-kernel@...r.kernel.org, keescook@...omium.org, tj@...nel.org,
avagin@...nvz.org, ebiederm@...ssion.com, hpa@...or.com,
serge.hallyn@...onical.com, xemul@...allels.com,
segoon@...nwall.com, kamezawa.hiroyu@...fujitsu.com,
mtk.manpages@...il.com, jln@...gle.com
Subject: Re: [patch 4/4] prctl: PR_SET_MM -- Introduce PR_SET_MM_MAP
operation, v3
On Sat, 23 Aug 2014 00:38:09 +0400 Cyrill Gorcunov <gorcunov@...il.com> wrote:
> >
> > Or will we? What happens if we later decide that some additional field
> > needs to be added? Do we version the interface? Add a new prctl()
> > mode? Let's cook up a plan for that and at least add to changelog?
>
> I don't expect to change it anytime soon but we still have an option --
> if we decide to extend or shrink it we always can use sizeof/offsetof
> helpers to check which exactly version userspace asks us to use.
How does that work? We just have a blob of bytes coming in from
userspace.
> As far as I understand the mm_struct is not the structure which
> changes that frequently, right?
We might find existing things which criu wants to access. And criu
lives forever, yes? The mm_struct is likely to change over that time
period ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists