From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 59459C64EC4 for ; Mon, 6 Mar 2023 17:29:40 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C53116B0071; Mon, 6 Mar 2023 12:29:39 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id C03586B0072; Mon, 6 Mar 2023 12:29:39 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AA3DC280001; Mon, 6 Mar 2023 12:29:39 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 98D736B0071 for ; Mon, 6 Mar 2023 12:29:39 -0500 (EST) Received: from smtpin23.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 6922A1C61FE for ; Mon, 6 Mar 2023 17:29:39 +0000 (UTC) X-FDA: 80539160478.23.7DAF136 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf12.hostedemail.com (Postfix) with ESMTP id 713714001E for ; Mon, 6 Mar 2023 17:29:36 +0000 (UTC) Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=jfDfCOyJ; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=TuxUQJJJ; dmarc=none; spf=pass (imf12.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1678123776; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=x2wJ/1+qCv7YJhFivtXnn5Inza/T/kAvFe4cwUGE/7M=; b=HAjyIkLfFj19CSuqdMl9oRUGtj7JsJJ0yFyxM8mVSNDm7yOEXCqj81Yam8y9yVdQDIDq4B Pd1w3icg5zLlSF+sQun5d1xGaym5/gS2Rw8EAnFSkyrle577AvqzuxNynq0ZBDXybJNY3f uW/IXhKfcstsiovyxM1kQDR56bhk2mc= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=jfDfCOyJ; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b=TuxUQJJJ; dmarc=none; spf=pass (imf12.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1678123776; a=rsa-sha256; cv=none; b=fFaPAMhiQcmAXwWgYnlx1k4szBZSlJof5WuSGAKmqLIJuFEohf1lKQXDzqRnvv/l9AAVxm 92LSNE4WCExYgVOPt5khQQVpoMjQ8wy1nzuuWaN+oAbQzm0PJkQ95CQK5F3x5gfSru2XbW VWl8jjT1G1n8SmCVYgBdbUx0kF9O4+s= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id B1FFC21C5B; Mon, 6 Mar 2023 17:29:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1678123774; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=x2wJ/1+qCv7YJhFivtXnn5Inza/T/kAvFe4cwUGE/7M=; b=jfDfCOyJy1ndJDHGQIejrU8vCh7aokmH29RLQCXz/jl890atMS2KY6sTEhqV4Yckagg0bq PS9XH+mp84EQV1Bp6Jfk2EvP76nXPDa1zWtkrWwQz5ZKRcXw7dsgPxJMA5YK4wY0jWU9F/ r/1w2r76fhQQ5T0ziaQka6JoReF2wLY= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1678123774; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=x2wJ/1+qCv7YJhFivtXnn5Inza/T/kAvFe4cwUGE/7M=; b=TuxUQJJJqSUaCGEdVCeXRRPvro8cH6NkICIu/rAz6JOQxhRwuqoXqM1Sw99mW9DAn31GN+ tui4w0zlhUozh0AA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 8217213A66; Mon, 6 Mar 2023 17:29:34 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id oVXAHv4iBmRScwAAMHmgww (envelope-from ); Mon, 06 Mar 2023 17:29:34 +0000 Message-ID: <6452176f-4c17-8e09-8561-c659cbea4014@suse.cz> Date: Mon, 6 Mar 2023 18:29:52 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH] mm, vmalloc: fix high order __GFP_NOFAIL allocations Content-Language: en-US To: Michal Hocko , Uladzislau Rezki Cc: Gao Xiang , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Mel Gorman , Baoquan He , Christoph Hellwig References: <20230305053035.1911-1-hsiangkao@linux.alibaba.com> From: Vlastimil Babka In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 713714001E X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: 35rod95n9dg8wteb11k1h4boxhr6pn1n X-HE-Tag: 1678123776-442742 X-HE-Meta: U2FsdGVkX1+/rtFMimWV0A+fjTd0cw7cIRTw/HWE2WL267EPgJfX796qyaqPP5UzElkDOhGpvSzytWySS9C8r6+jln1McbL9cnyNi0yRjH+/BaxYuwAt2BrP3xYJHMhtnHI0lEZpea73TE/J0v0KIMJtkMcrk5wB2RPuQMDHQ9DACwvLQqFL7QAzntEc77hL1iaYorb4Bey6XMDxVPd0ivi9/uv4xXzTrCJjrf/VXboNifle5/N5GI70XLoN4RhfNrPsTMdIOhOHM+QjMQ6drA/+QakTT0Rk9Mj0MaZGZX9azlcULCon1wmcXKoKqfw50maN6omp831KNtwne/yxaSe5YITFw/J9xsNf1bGRKCj7GnqtuhrrO+DDoX0T0C+iIM8jLlAgFH3pxFjOeo9cUk03CmWCAD1/peRdwFfmqhUGMuzwLvxDbdQrHSxp50p8lSIhZeHPE0K4pNjT4nVkbGFxedBWofTMpP1k2zSSu7AkOGWQAjFegRxagEfNcrcUH3AcM3RMGc+zCbzMLfULra4K/3S+HJeQvtbsdEOFiQpdTp8x/Cyp9FInzJm05W8rvquLLZmElr7/UR/GNyPbLKbUz0YPVOPtV11chGOnAD7viNJayJsj1qFbVBy7j72gqjCjx50BSrJczljF5njEJ2nriVzS9T81aIdkKaye5jPJUINVTAtxhGWlEQOQlIwLbzy2RV5PJBJinLh6o0ZzxWVTlcu/zy29T2tQKi623hXAz3kQ41xRJZ/FQXwmUCtfQhRuFKe3gEA6oUDVq4fPaCDeQt90w3DzPhfEW3Jvu4+m+fy2qV38jJkBoHIpKVSsTXX57It0PFAAGGDcXgd/vY/VHk2RaPvu03qiybS+k6p+mf1pXitbp0IJnperZXFomk2EOcNXSY0QPLEHoDI597ut2LGueljM5tFLycy4vg76Em2fgvdp7mO5GPy1DJnVLof5CIaZKZYbpT4Mszg dYinwnjE lqoV7/+EBtgH1o6MXlO7ODG9H7r9rbkTiYfmcfYRsCtHKDNztF8+keJdYssLVun1ZqILhkDCDy+xipQPbwZnb8/u5nz8z8M5GLZnMvaxMrDzGAiWPw+PGCc4csEk/br9yU0bcia4i8ZpjJpA329lsdQUoA0TKHXPKj50YvW6X3GG0NMA034P0NfF9IUXByjBr2d2dk0IjCJwsHLE9c8pFbcs4fOG6Y0S/aiC3G++2Yu/iyCrMolF+XPRhNm0HCWWfhlNh61LZ0tqU2+us3dbDR8oZCFj2+Q3El/Q+gEboqGrnHopHUQ488Rp+cG9BsOebl8v382/VFk3/Ec9K9WLDDb+Aug== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 3/6/23 15:03, Michal Hocko wrote: > --- > From 3ccfaa15bf2587b8998c129533a0404fedf5a484 Mon Sep 17 00:00:00 2001 > From: Michal Hocko > Date: Mon, 6 Mar 2023 09:15:17 +0100 > Subject: [PATCH] mm, vmalloc: fix high order __GFP_NOFAIL allocations > > Gao Xiang has reported that the page allocator complains about high > order __GFP_NOFAIL request coming from the vmalloc core: > > __alloc_pages+0x1cb/0x5b0 mm/page_alloc.c:5549 > alloc_pages+0x1aa/0x270 mm/mempolicy.c:2286 > vm_area_alloc_pages mm/vmalloc.c:2989 [inline] > __vmalloc_area_node mm/vmalloc.c:3057 [inline] > __vmalloc_node_range+0x978/0x13c0 mm/vmalloc.c:3227 > kvmalloc_node+0x156/0x1a0 mm/util.c:606 > kvmalloc include/linux/slab.h:737 [inline] > kvmalloc_array include/linux/slab.h:755 [inline] > kvcalloc include/linux/slab.h:760 [inline] > > it seems that I have completely missed high order allocation backing > vmalloc areas case when implementing __GFP_NOFAIL support. This means > that [k]vmalloc at al. can allocate higher order allocations with > __GFP_NOFAIL which can trigger OOM killer for non-costly orders easily > or cause a lot of reclaim/compaction activity if those requests cannot > be satisfied. > > Fix the issue by falling back to zero order allocations for __GFP_NOFAIL > requests if the high order request fails. > > Fixes: 9376130c390a ("mm/vmalloc: add support for __GFP_NOFAIL") > Reported-by: Gao Xiang > Signed-off-by: Michal Hocko Acked-by: Vlastimil Babka > --- > mm/vmalloc.c | 28 +++++++++++++++++++++++----- > 1 file changed, 23 insertions(+), 5 deletions(-) > > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index ef910bf349e1..bef6cf2b4d46 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -2883,6 +2883,8 @@ vm_area_alloc_pages(gfp_t gfp, int nid, > unsigned int order, unsigned int nr_pages, struct page **pages) > { > unsigned int nr_allocated = 0; > + gfp_t alloc_gfp = gfp; > + bool nofail = false; > struct page *page; > int i; > > @@ -2893,6 +2895,7 @@ vm_area_alloc_pages(gfp_t gfp, int nid, > * more permissive. > */ > if (!order) { > + /* bulk allocator doesn't support nofail req. officially */ > gfp_t bulk_gfp = gfp & ~__GFP_NOFAIL; > > while (nr_allocated < nr_pages) { > @@ -2931,20 +2934,35 @@ vm_area_alloc_pages(gfp_t gfp, int nid, > if (nr != nr_pages_request) > break; > } > + } else if (gfp & __GFP_NOFAIL) { > + /* > + * Higher order nofail allocations are really expensive and > + * potentially dangerous (pre-mature OOM, disruptive reclaim > + * and compaction etc. ^ unclosed parenthesis > + */ > + alloc_gfp &= ~__GFP_NOFAIL; > + nofail = true; > } > > /* High-order pages or fallback path if "bulk" fails. */ > - > while (nr_allocated < nr_pages) { > if (fatal_signal_pending(current)) > break; > > if (nid == NUMA_NO_NODE) > - page = alloc_pages(gfp, order); > + page = alloc_pages(alloc_gfp, order); > else > - page = alloc_pages_node(nid, gfp, order); > - if (unlikely(!page)) > - break; > + page = alloc_pages_node(nid, alloc_gfp, order); > + if (unlikely(!page)) { > + if (!nofail) > + break; > + > + /* fall back to the zero order allocations */ > + alloc_gfp |= __GFP_NOFAIL; > + order = 0; > + continue; > + } > + > /* > * Higher order allocations must be able to be treated as > * indepdenent small pages by callers (as they can with ^ while at it the typo could also be fixed