Received: by 10.223.185.116 with SMTP id b49csp5638625wrg; Wed, 7 Mar 2018 15:34:17 -0800 (PST) X-Google-Smtp-Source: AG47ELv1pgNEMiAdcbXCYqOdA5ESrZTCJNbNftZRcpPBrPcr01UT7JY9d0Gt3nPhYAl82/2Ae15Y X-Received: by 2002:a17:902:7d94:: with SMTP id a20-v6mr22133991plm.184.1520465657557; Wed, 07 Mar 2018 15:34:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520465657; cv=none; d=google.com; s=arc-20160816; b=PYXQQHsppdq6SVTJnlRgHTYr7sf1xWrGfCO9Cbp+OErhneUp2hWyZi/sgF02VQNQ+N ok1h4QZ0n+VTyke9TziYjvbrp9Wlh5/Zc4WoIuSe33V+D0ULinTm3lQVYa+kmNeobaSL LqHfJwgcv6eY8/qFKlnFF73xxz/9pp1LIWqEbJh8ZFMXEL2Atnf+iII1QwgWmPEJ4d91 gV5Z7nlWNrjYgxYQH7pBnK56uL91kkeraWC9BofifAsTjdXKcae/rYQ3T2/pljHEqtx2 iCiPKqMAmkWcFcQOQevufmfV3eV0oz1trIlCnwxwoBO+NJT2XLxWTGpBNcpMZizhB6bX taZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :arc-authentication-results; bh=2VcaKIQym1mPe055rCVY/o1sH9Pexlh23tP0g058tU0=; b=AP7M8RsjjiTHoS1OfWwzGCttzKP5b5wM7j7y2r+acuBQVSu7g6lWkMnLhsQ54B5s1u 9NQM8geaPLwMNDS9GMJ6RB9g86El+ClhwFSmaRygeDD+d7zu2Oiz/uI2QrcZwAyzbBvR xKU5Ksw89v53LmTemDDt4TNUsvoMqQYTySbnsC+CXGR7W6kZJtErUSPT8oEgEnYlF/k6 xmFk7eQBlB2TiAPLWm8IXeyLMVsokCwdkadYt7qpdkkWW5stD1YtB5Za+NpT56tkpNWH +j4bKulMRN04iH/4k6VkMbc9Ol60rxYiksKvTcAVnpsHxTsk4QRSe9ghuSQpJKZqhvTM oTMg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z9-v6si13879467pll.805.2018.03.07.15.34.03; Wed, 07 Mar 2018 15:34:17 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754944AbeCGXdH (ORCPT + 99 others); Wed, 7 Mar 2018 18:33:07 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:51582 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754745AbeCGXdG (ORCPT ); Wed, 7 Mar 2018 18:33:06 -0500 Received: from akpm3.svl.corp.google.com (unknown [104.133.9.71]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id EB90211D2; Wed, 7 Mar 2018 23:33:05 +0000 (UTC) Date: Wed, 7 Mar 2018 15:33:05 -0800 From: Andrew Morton To: Tetsuo Handa Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 (RESEND)] lockdep: Fix fs_reclaim warning. Message-Id: <20180307153305.16e5225d8a14d96436235eb1@linux-foundation.org> In-Reply-To: <201802280650.FJC73911.FOSOMLJVFFQtHO@I-love.SAKURA.ne.jp> References: <20180129102746.GQ2269@hirez.programming.kicks-ass.net> <201801292047.EHC05241.OHSQOJOVtFMFLF@I-love.SAKURA.ne.jp> <20180129135547.GR2269@hirez.programming.kicks-ass.net> <201802012036.FEE78102.HOMFFOtJVFOSQL@I-love.SAKURA.ne.jp> <201802082043.FFJ39503.SVQFFFOJMHLOtO@I-love.SAKURA.ne.jp> <201802280650.FJC73911.FOSOMLJVFFQtHO@I-love.SAKURA.ne.jp> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Feb 2018 06:50:02 +0900 Tetsuo Handa wrote: > > This warning is caused by commit d92a8cfcb37ecd13 ("locking/lockdep: Rework > FS_RECLAIM annotation") which replaced lockdep_set_current_reclaim_state()/ > lockdep_clear_current_reclaim_state() in __perform_reclaim() and > lockdep_trace_alloc() in slab_pre_alloc_hook() with fs_reclaim_acquire()/ > fs_reclaim_release(). Since __kmalloc_reserve() from __alloc_skb() adds > __GFP_NOMEMALLOC | __GFP_NOWARN to gfp_mask, and all reclaim path simply > propagates __GFP_NOMEMALLOC, fs_reclaim_acquire() in slab_pre_alloc_hook() > is trying to grab the 'fake' lock again when __perform_reclaim() already > grabbed the 'fake' lock. That's quite an audit trail. Shouldn't we be doing a cc:stable here? If so, which patch do we identify as being fixed, with "Fixes:"? d92a8cfcb37ecd13, I assume? I'd never even noticed fs_reclaim_acquire() and friends before. I do wish they had "lockdep" in their names, and a comment to explain what they do and why they exist.