Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:22786 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758553Ab3CDUyz (ORCPT ); Mon, 4 Mar 2013 15:54:55 -0500 Date: Mon, 4 Mar 2013 21:53:07 +0100 From: Oleg Nesterov To: Mandeep Singh Baines Cc: Jeff Layton , "Myklebust, Trond" , Ming Lei , "J. Bruce Fields" , Linux Kernel Mailing List , "linux-nfs@vger.kernel.org" , "Rafael J. Wysocki" , Andrew Morton , Tejun Heo , Ingo Molnar Subject: Re: LOCKDEP: 3.9-rc1: mount.nfs/4272 still has locks held! Message-ID: <20130304205307.GA13527@redhat.com> References: <4FA345DA4F4AE44899BD2B03EEEC2FA9286AD113@sacexcmbx05-prd.hq.netapp.com> <20130304092310.1d21100c@tlielax.poochiereds.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On 03/04, Mandeep Singh Baines wrote: > > The problem is that freezer_count() calls try_to_freeze(). In this > case, try_to_freeze() is not really adding any value. Well, I tend to agree. If a task calls __refrigerator() holding a lock which another freezable task can wait for, this is not freezer-friendly. freezable_schedule/freezer_do_not_count/etc not only means "I won't be active if freezing()", it should also mean "I won't block suspend/etc". OTOH, I understand that probably it is not trivial to change this code to make it freezer-friendly. But at least I disagree with "push your problems onto others". Oleg.