From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f67.google.com ([74.125.82.67]:33009 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752148AbdBFOHa (ORCPT ); Mon, 6 Feb 2017 09:07:30 -0500 From: Michal Hocko To: Andrew Morton , Cc: , Dave Chinner , djwong@kernel.org, "Theodore Ts'o" , Chris Mason , David Sterba , Jan Kara , ceph-devel@vger.kernel.org, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, logfs@logfs.org, linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org, reiserfs-devel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, linux-f2fs-devel@lists.sourceforge.net, linux-afs@lists.infradead.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-Id: <20170206140718.16222-1-mhocko@kernel.org> Sender: linux-btrfs-owner@vger.kernel.org List-ID: Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb@thunk.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Michal Hocko To: Andrew Morton , Cc: , Dave Chinner , djwong@kernel.org, "Theodore Ts'o" , Chris Mason , David Sterba , Jan Kara , ceph-devel@vger.kernel.org, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, logfs@logfs.org, linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org, reiserfs-devel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, linux-f2fs-devel@lists.sourceforge.net, linux-afs@lists.infradead.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-Id: <20170206140718.16222-1-mhocko@kernel.org> Sender: owner-linux-mm@kvack.org List-ID: Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb@thunk.org -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-ID: <20170206140718.16222-1-mhocko@kernel.org> Cc: , Dave Chinner , djwong-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, "Theodore Ts'o" , Chris Mason , David Sterba , Jan Kara , ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cluster-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, logfs-PCqxUs/MD9bYtjvyW6yDsg@public.gmane.org, linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, reiserfs-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ntfs-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-f2fs-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-afs-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka , Return-path: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-ext4.vger.kernel.org Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f67.google.com ([74.125.82.67]:33009 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752148AbdBFOHa (ORCPT ); Mon, 6 Feb 2017 09:07:30 -0500 From: Michal Hocko Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-Id: <20170206140718.16222-1-mhocko@kernel.org> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Andrew Morton , linux-fsdevel@vger.kernel.org Cc: linux-mm@kvack.org, Dave Chinner , djwong@kernel.org, Theodore Ts'o , Chris Mason , David Sterba , Jan Kara , ceph-devel@vger.kernel.org, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, logfs@logfs.org, linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org, reiserfs-devel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, linux-f2fs-devel@lists.sourceforge.net, linux-afs@lists.infradead.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb@thunk.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-ID: <20170206140718.16222-1-mhocko@kernel.org> Return-path: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andrew Morton , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Dave Chinner , djwong-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Theodore Ts'o , Chris Mason , David Sterba , Jan Kara , ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cluster-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, logfs-PCqxUs/MD9bYtjvyW6yDsg@public.gmane.org, linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, reiserfs-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-ntfs-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-f2fs-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-afs-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka List-Id: ceph-devel.vger.kernel.org Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-f198.google.com (mail-wj0-f198.google.com [209.85.210.198]) by kanga.kvack.org (Postfix) with ESMTP id BEE496B0069 for ; Mon, 6 Feb 2017 09:07:31 -0500 (EST) Received: by mail-wj0-f198.google.com with SMTP id kq3so18737511wjc.1 for ; Mon, 06 Feb 2017 06:07:31 -0800 (PST) Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com. [74.125.82.65]) by mx.google.com with ESMTPS id o64si8189710wmi.143.2017.02.06.06.07.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Feb 2017 06:07:28 -0800 (PST) Received: by mail-wm0-f65.google.com with SMTP id u63so22141624wmu.2 for ; Mon, 06 Feb 2017 06:07:28 -0800 (PST) From: Michal Hocko Subject: [PATCH 0/6 v4] scope GFP_NOFS api Date: Mon, 6 Feb 2017 15:07:12 +0100 Message-Id: <20170206140718.16222-1-mhocko@kernel.org> Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton , linux-fsdevel@vger.kernel.org Cc: linux-mm@kvack.org, Dave Chinner , djwong@kernel.org, Theodore Ts'o , Chris Mason , David Sterba , Jan Kara , ceph-devel@vger.kernel.org, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, logfs@logfs.org, linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-mtd@lists.infradead.org, reiserfs-devel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net, linux-f2fs-devel@lists.sourceforge.net, linux-afs@lists.infradead.org, LKML , Brian Foster , "Darrick J. Wong" , Michal Hocko , "Peter Zijlstra (Intel)" , Vlastimil Babka Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb@thunk.org -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Date: Mon, 6 Feb 2017 15:07:12 +0100 Subject: [Cluster-devel] [PATCH 0/6 v4] scope GFP_NOFS api Message-ID: <20170206140718.16222-1-mhocko@kernel.org> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I have posted the previous version here [1]. There are no real changes in the implementation since then. Few acks added and one new user of memalloc_noio_flags (in alloc_contig_range) converted. I have decided to drop the last two ext4 related patches. One of them will be picked up by Ted [2] and the other one will probably need more time to settle down. I believe it is OK as is but let's not block the whole thing just because of it. There didn't seem to be any real objections and so I think we should go and merge this to mmotm tree and target the next merge window. The risk of regressions is really small because we do not remove any real GFP_NOFS users yet. I hope to get ext4 parts resolved in the follow up patches as well as pull other filesystems in. There is still a lot work to do but having the infrastructure in place should be very useful already. The patchset is based on next-20170206 Diffstat says fs/jbd2/journal.c | 7 +++++++ fs/jbd2/transaction.c | 11 +++++++++++ fs/xfs/kmem.c | 12 ++++++------ fs/xfs/kmem.h | 2 +- fs/xfs/libxfs/xfs_btree.c | 2 +- fs/xfs/xfs_aops.c | 6 +++--- fs/xfs/xfs_buf.c | 8 ++++---- fs/xfs/xfs_trans.c | 12 ++++++------ include/linux/gfp.h | 18 +++++++++++++++++- include/linux/jbd2.h | 2 ++ include/linux/sched.h | 32 ++++++++++++++++++++++++++------ kernel/locking/lockdep.c | 6 +++++- lib/radix-tree.c | 2 ++ mm/page_alloc.c | 10 ++++++---- mm/vmscan.c | 6 +++--- 15 files changed, 100 insertions(+), 36 deletions(-) Shortlog: Michal Hocko (6): lockdep: allow to disable reclaim lockup detection xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS mm: introduce memalloc_nofs_{save,restore} API xfs: use memalloc_nofs_{save,restore} instead of memalloc_noio* jbd2: mark the transaction context with the scope GFP_NOFS context jbd2: make the whole kjournald2 kthread NOFS safe [1] http://lkml.kernel.org/r/20170106141107.23953-1-mhocko at kernel.org [2] http://lkml.kernel.org/r/20170117030118.727jqyamjhojzajb at thunk.org