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 X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 350DFC55179 for ; Thu, 5 Nov 2020 14:02:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AE1E122203 for ; Thu, 5 Nov 2020 14:02:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="KeEMdK6F" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731013AbgKEOC3 (ORCPT ); Thu, 5 Nov 2020 09:02:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40236 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730871AbgKEOC3 (ORCPT ); Thu, 5 Nov 2020 09:02:29 -0500 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA812C0613CF; Thu, 5 Nov 2020 06:02:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cD+eBYuUgW3bthVlBrXo+FI4A/dPV76Q94+GqMIroAA=; b=KeEMdK6FSs5d8bD8m7s0IrwI1S BnlylR6ITz29Uf5Ptcqq+iIjjeqZV8yePLzr6gmRSRJIVF4G+zLMA7VhEwXeyQmEc71RUQ9HBXLle hDH9Tok/1Re9tI9E/AlP127uY7UbbAMqO2b+cFW30SFAbkRXA96Z5ADy5faCwZRLaHr5C65KoFjKJ uKPLxs423qYunSWDIUnlITZQDIWNsvsl5MC9FvsykLF+CulJZuBAvfaszw8roRjzIdK3PILvwj/kc GB+sEbokt6ofDsyrELe8nY5hTseOlaWkiUO67+NGaqlhBbbKthBSk+chzwco9TW5n7WV0NYnFRq+i iol8H7xw==; Received: from willy by casper.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kafqL-0003KJ-1f; Thu, 05 Nov 2020 14:02:25 +0000 Date: Thu, 5 Nov 2020 14:02:24 +0000 From: Matthew Wilcox To: Eric Dumazet Cc: linux-mm@kvack.org, netdev@vger.kernel.org, Dongli Zhang , Aruna Ramakrishna , Bert Barbe , Rama Nichanamatlu , Venkat Venkatsubra , Manjunath Patil , Joe Jin , SRINIVAS , stable@vger.kernel.org Subject: Re: [PATCH] page_frag: Recover from memory pressure Message-ID: <20201105140224.GK17076@casper.infradead.org> References: <20201105042140.5253-1-willy@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Nov 05, 2020 at 02:21:25PM +0100, Eric Dumazet wrote: > On 11/5/20 5:21 AM, Matthew Wilcox (Oracle) wrote: > > When the machine is under extreme memory pressure, the page_frag allocator > > signals this to the networking stack by marking allocations with the > > 'pfmemalloc' flag, which causes non-essential packets to be dropped. > > Unfortunately, even after the machine recovers from the low memory > > condition, the page continues to be used by the page_frag allocator, > > so all allocations from this page will continue to be dropped. > > > > Fix this by freeing and re-allocating the page instead of recycling it. > > > > Reported-by: Dongli Zhang > > Cc: Aruna Ramakrishna > > Cc: Bert Barbe > > Cc: Rama Nichanamatlu > > Cc: Venkat Venkatsubra > > Cc: Manjunath Patil > > Cc: Joe Jin > > Cc: SRINIVAS > > Cc: stable@vger.kernel.org > > Fixes: 79930f5892e ("net: do not deplete pfmemalloc reserve") > > Your patch looks fine, although this Fixes: tag seems incorrect. > > 79930f5892e ("net: do not deplete pfmemalloc reserve") was propagating > the page pfmemalloc status into the skb, and seems correct to me. > > The bug was the page_frag_alloc() was keeping a problematic page for > an arbitrary period of time ? Isn't this the commit which unmasks the problem, though? I don't think it's the buggy commit, but if your tree doesn't have 79930f5892e, then you don't need this patch. Or are you saying the problem dates back all the way to c93bdd0e03e8 ("netvm: allow skb allocation to use PFMEMALLOC reserves") > > + if (nc->pfmemalloc) { > > if (unlikely(nc->pfmemalloc)) { ACK. Will make the change once we've settled on an appropriate Fixes tag.