Re: [PATCH 3/3] nsproxy: support CLONE_NEWTIME with setns()

2020-06-25 Thread Christian Brauner
On Thu, Jun 25, 2020 at 02:06:18AM -0700, Andrei Vagin wrote: > On Fri, Jun 19, 2020 at 05:35:59PM +0200, Christian Brauner wrote: > > So far setns() was missing time namespace support. This was partially due > > to it simply not being implemented but also because vdso_join_timens() > > could still

Re: [PATCH 3/3] nsproxy: support CLONE_NEWTIME with setns()

2020-06-25 Thread Andrei Vagin
On Fri, Jun 19, 2020 at 05:35:59PM +0200, Christian Brauner wrote: > So far setns() was missing time namespace support. This was partially due > to it simply not being implemented but also because vdso_join_timens() > could still fail which made switching to multiple namespaces atomically > problem

Re: [PATCH 3/3] nsproxy: support CLONE_NEWTIME with setns()

2020-06-25 Thread Andrei Vagin
On Tue, Jun 23, 2020 at 01:55:21PM +0200, Christian Brauner wrote: > On Fri, Jun 19, 2020 at 05:35:59PM +0200, Christian Brauner wrote: > > So far setns() was missing time namespace support. This was partially due > > to it simply not being implemented but also because vdso_join_timens() > > could

Re: [PATCH 3/3] nsproxy: support CLONE_NEWTIME with setns()

2020-06-23 Thread Christian Brauner
On Fri, Jun 19, 2020 at 05:35:59PM +0200, Christian Brauner wrote: > So far setns() was missing time namespace support. This was partially due > to it simply not being implemented but also because vdso_join_timens() > could still fail which made switching to multiple namespaces atomically > problem

[PATCH 3/3] nsproxy: support CLONE_NEWTIME with setns()

2020-06-19 Thread Christian Brauner
So far setns() was missing time namespace support. This was partially due to it simply not being implemented but also because vdso_join_timens() could still fail which made switching to multiple namespaces atomically problematic. This is now fixed so support CLONE_NEWTIME with setns() Cc: Thomas G