On Wed, Apr 04, 2018 at 08:54:59AM -0700, Yang Shi wrote:
> > Yeah, let's just drop it and have the patch in linux-next (via mmotm)
> > for 2 release cycles and see whether somebody complains.
>
> BTW, I will do my v3 on top of the patch (drop off prctl_set_mm).
Sorry for delay, will do in a
On Wed, Apr 04, 2018 at 08:54:59AM -0700, Yang Shi wrote:
> > Yeah, let's just drop it and have the patch in linux-next (via mmotm)
> > for 2 release cycles and see whether somebody complains.
>
> BTW, I will do my v3 on top of the patch (drop off prctl_set_mm).
Sorry for delay, will do in a
On 4/3/18 10:35 PM, Michal Hocko wrote:
On Tue 03-04-18 16:15:20, Yang Shi wrote:
On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
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
On 4/3/18 10:35 PM, Michal Hocko wrote:
On Tue 03-04-18 16:15:20, Yang Shi wrote:
On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
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
On Wed, Apr 04, 2018 at 07:35:41AM +0200, Michal Hocko wrote:
> > > Or we can simply drop it off because PR_SET_MM_MAP covers all needs,
> > > and I would rather prefer to do that asap.
> >
> > Thanks for making it deprecated. I'd prefer just drop it off if nobody
> > objects. The change will get
On Wed, Apr 04, 2018 at 07:35:41AM +0200, Michal Hocko wrote:
> > > Or we can simply drop it off because PR_SET_MM_MAP covers all needs,
> > > and I would rather prefer to do that asap.
> >
> > Thanks for making it deprecated. I'd prefer just drop it off if nobody
> > objects. The change will get
On Tue 03-04-18 16:15:20, Yang Shi wrote:
>
>
> On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
> > 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
On Tue 03-04-18 16:15:20, Yang Shi wrote:
>
>
> On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
> > 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
On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
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
On 4/3/18 3:37 PM, Cyrill Gorcunov wrote:
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
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
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
12 matches
Mail list logo
