Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-12-08 Thread Eric W. Biederman
Nikolay Borisov writes: > On 8.12.2016 08:58, Nikolay Borisov wrote: >> >> >> On 8.12.2016 03:40, Eric W. Biederman wrote: >>> Nikolay Borisov writes: >>> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully resolved. >>> >>> After getting slowed down by some fi

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-12-08 Thread Eric W. Biederman
Nikolay Borisov writes: > On 8.12.2016 03:40, Eric W. Biederman wrote: >> Nikolay Borisov writes: >> >>> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >>> resolved. >> >> After getting slowed down by some fixes I am now taking a hard look at >> your patch in the hop

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-12-08 Thread Nikolay Borisov
On 8.12.2016 08:58, Nikolay Borisov wrote: > > > On 8.12.2016 03:40, Eric W. Biederman wrote: >> Nikolay Borisov writes: >> >>> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >>> resolved. >> >> After getting slowed down by some fixes I am now taking a hard look at

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-12-07 Thread Nikolay Borisov
On 8.12.2016 03:40, Eric W. Biederman wrote: > Nikolay Borisov writes: > >> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >> resolved. > > After getting slowed down by some fixes I am now taking a hard look at > your patch in the hopes of merging it. > > Did you ha

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-12-07 Thread Eric W. Biederman
Nikolay Borisov writes: > Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully > resolved. After getting slowed down by some fixes I am now taking a hard look at your patch in the hopes of merging it. Did you happen to see the kbuild test roboot boot failures and did you hap

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-11-13 Thread Serge E. Hallyn
On Tue, Oct 11, 2016 at 10:36:22AM +0300, Nikolay Borisov wrote: > This patchset converts inotify to using the newly introduced > per-userns sysctl infrastructure. > > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where multip

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-10-27 Thread Eric W. Biederman
Nikolay Borisov writes: > On 10/11/2016 10:36 AM, Nikolay Borisov wrote: >> This patchset converts inotify to using the newly introduced >> per-userns sysctl infrastructure. >> >> Currently the inotify instances/watches are being accounted in the >> user_struct structure. This means that in setu

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-10-24 Thread Jan Kara
On Tue 11-10-16 10:36:22, Nikolay Borisov wrote: > This patchset converts inotify to using the newly introduced > per-userns sysctl infrastructure. > > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where multiple > users in un

Re: [PATCH v2] inotify: Convert to using per-namespace limits

2016-10-23 Thread Nikolay Borisov
On 10/11/2016 10:36 AM, Nikolay Borisov wrote: > This patchset converts inotify to using the newly introduced > per-userns sysctl infrastructure. > > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where multiple > users in un

[PATCH v2] inotify: Convert to using per-namespace limits

2016-10-11 Thread Nikolay Borisov
This patchset converts inotify to using the newly introduced per-userns sysctl infrastructure. Currently the inotify instances/watches are being accounted in the user_struct structure. This means that in setups where multiple users in unprivileged containers map to the same underlying real user (i