From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Andrey Vagin <avagin@openvz.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Yang Shi <yang.shi@linux.alibaba.com>
Subject: Re: [PATCH v2] prctl: Deprecate non PR_SET_MM_MAP operations
Date: Wed, 18 Apr 2018 15:28:20 -0700 [thread overview]
Message-ID: <20180418152820.e8f317534c01696d4835a40f@linux-foundation.org> (raw)
In-Reply-To: <20180405182651.GM15783@uranus.lan>
On Thu, 5 Apr 2018 21:26:51 +0300 Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> Subject: [PATCH v2] prctl: Deprecate non PR_SET_MM_MAP operations
s/Deprecate/remove/ !
> An ability to manipulate mm_struct fields was introduced in
> sake of CRIU in first place. Later we provide more suitable
> and safe operation PR_SET_MM_MAP where all fields to be modifed
> are passed in one structure which allows us to make more detailed
> verification.
>
> Still old interface remains present for compatibility reason
> though CRIU itself already switched to PR_SET_MM_MAP on its
> own long ago.
>
> Googling didn't reveal some other users of this operation
> so I think it should be safe to remove this interface.
It does seem a bit sudden. We could just add a "this interface is
scheduled for removal" warning, then delete the code for real later in
the year. To give people time to migrate or to complain to us.
next prev parent reply other threads:[~2018-04-18 22:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 18:26 [PATCH v2] prctl: Deprecate non PR_SET_MM_MAP operations Cyrill Gorcunov
2018-04-05 18:56 ` Michal Hocko
2018-04-05 19:51 ` Cyrill Gorcunov
2018-04-05 18:59 ` Yang Shi
2018-04-18 22:28 ` Andrew Morton [this message]
2018-04-18 22:42 ` Cyrill Gorcunov
2018-04-20 2:38 ` [v2] " Sergey Senozhatsky
2018-04-20 7:02 ` Cyrill Gorcunov
2018-04-20 7:29 ` Sergey Senozhatsky
2018-04-20 8:18 ` Cyrill Gorcunov
2018-04-20 20:37 ` [PATCH] prctl: Don't compile some of prctl functions when CRUI kbuild test robot
2018-04-20 21:00 ` Andrew Morton
2019-04-17 12:23 ` Michal Koutný
2019-04-17 12:38 ` Cyrill Gorcunov
2019-04-17 14:44 ` Michal Koutný
2019-04-17 14:56 ` Cyrill Gorcunov
2019-04-17 16:56 ` Cyrill Gorcunov
2018-04-20 21:43 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180418152820.e8f317534c01696d4835a40f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akpm@linuxfoundation.org \
--cc=avagin@openvz.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rdunlap@infradead.org \
--cc=xemul@virtuozzo.com \
--cc=yang.shi@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).