Re: [PATCH v3 2/3] kernel/ucounts: expose count of inotify watches in use

On Sat, Jun 1, 2019 at 8:20 PM Albert Vaca Cintora wrote: > > On Sat, Jun 1, 2019 at 2:00 AM Andrew Morton > wrote: > > > > On Fri, 31 May 2019 21:50:15 +0200 Albert Vaca Cintora > > wrote: > > > > > Adds a readonly 'current_inotify_watches' entry to the user sysctl table. > > > The handler f

Re: [PATCH v3 2/3] kernel/ucounts: expose count of inotify watches in use

On Sat, Jun 1, 2019 at 2:00 AM Andrew Morton wrote: > > On Fri, 31 May 2019 21:50:15 +0200 Albert Vaca Cintora > wrote: > > > Adds a readonly 'current_inotify_watches' entry to the user sysctl table. > > The handler for this entry is a custom function that ends up calling > > proc_dointvec. Said

Re: [PATCH v3 2/3] kernel/ucounts: expose count of inotify watches in use

On Fri, 31 May 2019 21:50:15 +0200 Albert Vaca Cintora wrote: > Adds a readonly 'current_inotify_watches' entry to the user sysctl table. > The handler for this entry is a custom function that ends up calling > proc_dointvec. Said sysctl table already contains 'max_inotify_watches' > and it gets

[PATCH v3 2/3] kernel/ucounts: expose count of inotify watches in use

Adds a readonly 'current_inotify_watches' entry to the user sysctl table. The handler for this entry is a custom function that ends up calling proc_dointvec. Said sysctl table already contains 'max_inotify_watches' and it gets mounted under /proc/sys/user/. Inotify watches are a finite resource, i