The patch titled
Subject: fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch.cleanup
has been added to the -mm tree. Its filename is
fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Shakeel Butt <shakeelb@xxxxxxxxxx>
Subject: fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch.cleanup
use GFP_KERNEL_ACCOUNT rather than open-coding it
Link: http://lkml.kernel.org/r/20180702215439.211597-1-shakeelb@xxxxxxxxxx
Signed-off-by: Shakeel Butt <shakeelb@xxxxxxxxxx>
Cc: Michal Hocko <mhocko@xxxxxxxxxx>
Cc: Jan Kara <jack@xxxxxxx>
Cc: Amir Goldstein <amir73il@xxxxxxxxx>
Cc: Greg Thelen <gthelen@xxxxxxxxxx>
Cc: Johannes Weiner <hannes@xxxxxxxxxxx>
Cc: Vladimir Davydov <vdavydov.dev@xxxxxxxxx>
Cc: Roman Gushchin <guro@xxxxxx>
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/notify/fanotify/fanotify.c | 2 +-
fs/notify/inotify/inotify_fsnotify.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -puN fs/notify/fanotify/fanotify.c~fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix fs/notify/fanotify/fanotify.c
--- a/fs/notify/fanotify/fanotify.c~fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix
+++ a/fs/notify/fanotify/fanotify.c
@@ -142,7 +142,7 @@ struct fanotify_event_info *fanotify_all
const struct path *path)
{
struct fanotify_event_info *event = NULL;
- gfp_t gfp = GFP_KERNEL | __GFP_ACCOUNT;
+ gfp_t gfp = GFP_KERNEL_ACCOUNT;
/*
* For queues with unlimited length lost events are not expected and
diff -puN fs/notify/inotify/inotify_fsnotify.c~fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix fs/notify/inotify/inotify_fsnotify.c
--- a/fs/notify/inotify/inotify_fsnotify.c~fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix
+++ a/fs/notify/inotify/inotify_fsnotify.c
@@ -101,7 +101,7 @@ int inotify_handle_event(struct fsnotify
/* Whoever is interested in the event, pays for the allocation. */
memalloc_use_memcg(group->memcg);
- event = kmalloc(alloc_len, GFP_KERNEL | __GFP_ACCOUNT);
+ event = kmalloc(alloc_len, GFP_KERNEL_ACCOUNT);
memalloc_unuse_memcg();
if (unlikely(!event)) {
_
Patches currently in -mm which might be from shakeelb@xxxxxxxxxx are
slub-track-number-of-slabs-irrespective-of-config_slub_debug.patch
kvm-mm-account-shadow-page-tables-to-kmemcg.patch
kvm-mm-account-shadow-page-tables-to-kmemcg-v2.patch
fs-fsnotify-account-fsnotify-metadata-to-kmemcg.patch
fs-fsnotify-account-fsnotify-metadata-to-kmemcg-fix.patch
fs-mm-account-buffer_head-to-kmemcg.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
