On Sun, Aug 11, 2019 at 09:06:59PM +0200, Christian Brauner wrote:
> On Sun, Aug 11, 2019 at 08:51:48AM +0200, Christian Brauner wrote:
> > On Sat, Aug 10, 2019 at 07:59:18AM +0200, Adrian Reber wrote:
> > > On Sat, Aug 10, 2019 at 03:10:34AM +0200, Christian Brauner wrote:
> > > > On Thu, Aug 08,
On Sun, Aug 11, 2019 at 08:51:48AM +0200, Christian Brauner wrote:
> On Sat, Aug 10, 2019 at 07:59:18AM +0200, Adrian Reber wrote:
> > On Sat, Aug 10, 2019 at 03:10:34AM +0200, Christian Brauner wrote:
> > > On Thu, Aug 08, 2019 at 11:22:21PM +0200, Adrian Reber wrote:
> > > > The main motivation t
On Sat, Aug 10, 2019 at 07:59:18AM +0200, Adrian Reber wrote:
> On Sat, Aug 10, 2019 at 03:10:34AM +0200, Christian Brauner wrote:
> > On Thu, Aug 08, 2019 at 11:22:21PM +0200, Adrian Reber wrote:
> > > The main motivation to add set_tid to clone3() is CRIU.
> > >
> > > To restore a process with t
On Sat, Aug 10, 2019 at 03:10:34AM +0200, Christian Brauner wrote:
> On Thu, Aug 08, 2019 at 11:22:21PM +0200, Adrian Reber wrote:
> > The main motivation to add set_tid to clone3() is CRIU.
> >
> > To restore a process with the same PID/TID CRIU currently uses
> > /proc/sys/kernel/ns_last_pid. It
On Thu, Aug 08, 2019 at 11:22:21PM +0200, Adrian Reber wrote:
> The main motivation to add set_tid to clone3() is CRIU.
>
> To restore a process with the same PID/TID CRIU currently uses
> /proc/sys/kernel/ns_last_pid. It writes the desired (PID - 1) to
> ns_last_pid and then (quickly) does a clon
The main motivation to add set_tid to clone3() is CRIU.
To restore a process with the same PID/TID CRIU currently uses
/proc/sys/kernel/ns_last_pid. It writes the desired (PID - 1) to
ns_last_pid and then (quickly) does a clone(). This works most of the
time, but it is racy. It is also slow as it
6 matches
Mail list logo