Re: [RESEND PATCH v2 2/2] memcg, fsnotify: no oom-kill for remote memcg charging

2019-05-13 Thread Michal Hocko
On Sun 12-05-19 09:09:27, Shakeel Butt wrote: [...] > diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c > index 6b9c27548997..f78fd4c8f12d 100644 > --- a/fs/notify/fanotify/fanotify.c > +++ b/fs/notify/fanotify/fanotify.c > @@ -288,10 +288,13 @@ struct fanotify_event

[RESEND PATCH v2 2/2] memcg, fsnotify: no oom-kill for remote memcg charging

2019-05-12 Thread Shakeel Butt
The commit d46eb14b735b ("fs: fsnotify: account fsnotify metadata to kmemcg") added remote memcg charging for fanotify and inotify event objects. The aim was to charge the memory to the listener who is interested in the events but without triggering the OOM killer. Otherwise there would be