From: Richard Weinberger Subject: Re: vmalloc with GFP_NOFS Date: Tue, 24 Apr 2018 21:10:08 +0200 Message-ID: <1912881.zKmfqiQKhD@blindfold> References: <20180424162712.GL17484@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: LKML , Artem Bityutskiy , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Cyrille Pitchen , Theodore Ts'o , Andreas Dilger , Steven Whitehouse , Bob Peterson , Trond Myklebust , Anna Schumaker , Adrian Hunter , Philippe Ombredanne , Kate Stewart , Mikulas Patocka , linux-mtd@lists.infradead.org, linux-ext4@vger.k To: Michal Hocko Return-path: In-Reply-To: <20180424162712.GL17484@dhcp22.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org [resending without html ...] Am Dienstag, 24. April 2018, 18:27:12 CEST schrieb Michal Hocko: > Hi, > it seems that we still have few vmalloc users who perform GFP_NOFS > allocation: > drivers/mtd/ubi/io.c UBI is not a big deal. We use it here like in UBIFS for debugging when self-checks are enabled. > fs/ext4/xattr.c > fs/gfs2/dir.c > fs/gfs2/quota.c > fs/nfs/blocklayout/extent_tree.c > fs/ubifs/debug.c > fs/ubifs/lprops.c > fs/ubifs/lpt_commit.c > fs/ubifs/orphan.c All users in UBIFS are debugging code and some error reporting. No fast paths. I think we can switch to prealloation + locking without much hassle. I can prepare a patch. Thanks, //richard