Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3491828imm; Tue, 17 Jul 2018 05:52:32 -0700 (PDT) X-Google-Smtp-Source: AAOMgpeXup45UXJQI9OqFP9fE998VRHWgES3UzoCoU5jG1I4sLCWgv1Or3vPbPWgJjplyPBb8guQ X-Received: by 2002:a17:902:6902:: with SMTP id j2-v6mr1495108plk.323.1531831952168; Tue, 17 Jul 2018 05:52:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531831952; cv=none; d=google.com; s=arc-20160816; b=NR1xNJyKuWASQ9FinSL50HsUu4FGIR1acrLeLhnwrjYYzHpRmDqeToWNNK1SwDcDl2 XQ5qOg3zNyH6TfBbfHhpCs0e1JSBRM/ctgvhGVHl/SliVhKijj/GNzTgbly+3Bf+TGGM GEXMsp//IXXAosXImHKMCtzHBWfTAmSeIvfK/NC8KeAVn0rusCyjvUYs2B97H/jTDrmN X66lETARHJGNYBG800bdGgKB/dq6Iw0Gbbr7bMS+HbqeFrqW1ALNN6y3OYyXY8QXMrOR bknmW1E8LizKzcaQrw4af34yCpRr0rY1YjP5oigrIhyGozdo73VXgfiKZ/0trGSdoXHs HdWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=DZ369sYo5rijeN0SpATVIasDXQeYkAYfspIiMboseB4=; b=NzVYARfiM9+6DgMDdn7+ojrkyC4eRlYaY6Gu3aaU4JZcR0YeuuA1o2VAuFtAXXcU6w PWX00474ksrcmSsaCaizYC5e7Pxay6RgfMf75rVINT9FwxSTJMDLMecGZqmMOT02P3e5 AXwYUjKybw172KynPPBQtHbybBYqINd98lgPyNff28KTODejGm4VRGl1ER2yg00Nx88P kAkxBYkp1ZQJvF2ALzrK4SMyWzuihkfOgJXISNF9N468Cd+UY087R5UtU3UUaUeXpvFX 0UIypSN4f/JzfxiNQvDn9ItxsO9jSiOBJzzVrG3BE7KXT1napGvaiyh5TpSx8nRoPZyk 8grg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m86-v6si891897pfj.48.2018.07.17.05.52.17; Tue, 17 Jul 2018 05:52:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731593AbeGQNXd (ORCPT + 99 others); Tue, 17 Jul 2018 09:23:33 -0400 Received: from mx2.suse.de ([195.135.220.15]:56122 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731429AbeGQNXd (ORCPT ); Tue, 17 Jul 2018 09:23:33 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D7B2BAECA; Tue, 17 Jul 2018 12:50:59 +0000 (UTC) Date: Tue, 17 Jul 2018 14:50:59 +0200 From: Michal Hocko To: Steven Whitehouse Cc: LKML , Artem Bityutskiy , Richard Weinberger , David Woodhouse , Brian Norris , Boris Brezillon , Marek Vasut , Cyrille Pitchen , Theodore Ts'o , Andreas Dilger , Bob Peterson , Trond Myklebust , Anna Schumaker , Adrian Hunter , Philippe Ombredanne , Kate Stewart , Mikulas Patocka , linux-mtd@lists.infradead.org, linux-ext4@vger.kernel.org, cluster-devel@redhat.com, linux-nfs@vger.kernel.org, linux-mm@kvack.org Subject: Re: vmalloc with GFP_NOFS Message-ID: <20180717125059.GC30926@dhcp22.suse.cz> References: <20180424162712.GL17484@dhcp22.suse.cz> <20180424200927.GU17484@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180424200927.GU17484@dhcp22.suse.cz> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 24-04-18 14:09:27, Michal Hocko wrote: > On Tue 24-04-18 20:26:23, Steven Whitehouse wrote: > [...] > > It would be good to fix this, and it has been known as an issue for a long > > time. We might well be able to make use of the new API though. It might be > > as simple as adding the calls when we get & release glocks, but I'd have to > > check the code to be sure, > > Yeah, starting with annotating those locking contexts and how document > how their are used in the reclaim is the great first step. This has to > be done per-fs obviously. Any chance of progress here? -- Michal Hocko SUSE Labs