From: Michal Hocko Subject: Re: vmalloc with GFP_NOFS Date: Thu, 10 May 2018 07:58:25 +0200 Message-ID: <20180510055825.GB32366@dhcp22.suse.cz> References: <20180424162712.GL17484@dhcp22.suse.cz> <20180424183536.GF30619@thunk.org> <20180424192542.GS17484@dhcp22.suse.cz> <20180509134222.GU32366@dhcp22.suse.cz> <20180509151351.GA4111@magnolia> <20180509210447.GX32366@dhcp22.suse.cz> <20180509220231.GD25312@magnolia> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Theodore Y. Ts'o" , LKML , Artem Bityutskiy , Richard Weinberger , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Cyrille Pitchen , Andreas Dilger , Steven Whitehouse , Bob Peterson , Trond Myklebust , Anna Schumaker , Adrian Hunter , Philippe Ombredanne , Kate Stewart , Mikulas Patocka , To: "Darrick J. Wong" Return-path: Content-Disposition: inline In-Reply-To: <20180509220231.GD25312@magnolia> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Wed 09-05-18 15:02:31, Darrick J. Wong wrote: > On Wed, May 09, 2018 at 11:04:47PM +0200, Michal Hocko wrote: > > On Wed 09-05-18 08:13:51, Darrick J. Wong wrote: [...] > > > > FS resp. IO submitting code paths have to be careful when allocating > > > > > > Not sure what 'FS resp. IO' means here -- 'FS and IO' ? > > > > > > (Or is this one of those things where this looks like plain English text > > > but in reality it's some sort of markup that I'm not so familiar with?) > > > > > > Confused because I've seen 'resp.' used as shorthand for > > > 'responsible'... > > > > Well, I've tried to cover both. Filesystem and IO code paths which > > allocate while in sensitive context. IO submission is kinda clear but I > > am not sure what a general term for filsystem code paths would be. I > > would be greatful for any hints here. > > "Code paths in the filesystem and IO stacks must be careful when > allocating memory to prevent recursion deadlocks caused by direct memory > reclaim calling back into the FS or IO paths and blocking on already > held resources (e.g. locks)." ? Great, thanks! -- Michal Hocko SUSE Labs