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 9D09B6B0038 for ; Fri, 16 Dec 2016 07:46:43 -0500 (EST) Received: by mail-wj0-f198.google.com with SMTP id o2so34831690wje.5 for ; Fri, 16 Dec 2016 04:46:43 -0800 (PST) Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com. [74.125.82.68]) by mx.google.com with ESMTPS id y65si3204493wmb.15.2016.12.16.04.46.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Dec 2016 04:46:41 -0800 (PST) Received: by mail-wm0-f68.google.com with SMTP id u144so5264494wmu.0 for ; Fri, 16 Dec 2016 04:46:40 -0800 (PST) From: Michal Hocko Subject: [DEBUG PATCH 0/2] debug explicit GFP_NO{FS,IO} usage from the scope context Date: Fri, 16 Dec 2016 13:46:26 +0100 Message-Id: <20161216124628.26846-1-mhocko@kernel.org> In-Reply-To: <20161215140715.12732-1-mhocko@kernel.org> References: <20161215140715.12732-1-mhocko@kernel.org> Sender: owner-linux-mm@kvack.org List-ID: To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org Cc: Andrew Morton , Dave Chinner , 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 Hi, I've forgot to add the following two patches which should help to identify explicit GFP_NO{FS,IO} usage from withing a scope context. Such a usage can be changed to the full GFP_KERNEL because all the calls from within the NO{FS,IO} scope will drop the __GFP_FS resp. __GFP_IO automatically and if the function is called outside of the scope then we do not need to restrict it to NOFS/NOIO as long as all the reclaim recursion unsafe contexts are marked properly. This means that each such a reported allocation site has to be checked before converted. The debugging has to be enabled explicitly by a kernel command line parameter and then it reports the stack trace of the allocation and also the function which has started the current scope. These two patches are _not_ intended to be merged and they are only aimed at debugging. -- 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