Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp404651ybl; Wed, 11 Dec 2019 01:32:38 -0800 (PST) X-Google-Smtp-Source: APXvYqzfOPSL8jCxX/kkZoTpihZlJaMAFuL7tzPrKDNBwY298RjrUHpsicuTOVEApvy4VFZkJ06y X-Received: by 2002:a05:6830:12cc:: with SMTP id a12mr1425226otq.73.1576056758136; Wed, 11 Dec 2019 01:32:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576056758; cv=none; d=google.com; s=arc-20160816; b=AUBA3NFMDiiGcfD9DLf3GseBm3E0aXlHIAvhswmTE3wQAngqATakInBq22qiAtziPe 6pcd04i9er7E+qm5oABxkqiuwazlG7wmEgBwix06TbsnyNqgRS920JuYCXlZdhvECiEa a2aO3dCHghkZGZUZ/WIbKbUSjfxu2VwP3DPHVeeRrEBh6vMxT/aPiGa+3CujgnVxXgRW ePp9RofFERInoxBSyBTioKwgyOCWMUbRN2YMTOaWjWI+L9eY+xtyI1q+BIX3ykuBDM8h 1lp2gYy+VcMnVdzS3yF7pzppgMRcfddbsy1u7zktWZ+0YGjDqsBX/6cqti/23jGsMpIq kU/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :organization:in-reply-to:subject:cc:to:from; bh=xIfy6ZBmCczjgzZqdjyjH6ISko9GcMsi8lsPtmvzUOM=; b=Ee35OYL9fTZnn2MLS5BhopAt+UAqTbBBqbtrk/ZZ2+1fycQLT7JU/FHKT+PFyyaAIU EM+ZvRjVQZeXZ4Fk3oILb/7EtYTDnRl2uZJXRdRBLj2hGZ6gchiOr5kEjprbgliga5ma gTuWW0M9Fww1i/PDK0K02FTLBP5kERbhbnWXl5gJurlwUPeSfxkDneJ+to2pN8/rpD2h 09tGUO5eKXQgStWBxNf4i/hLhRh7vWOUDrpblyel0i9kJNiy7nxmMITyfxzAowQX5zJ1 6ks0sGE2F0oTwK4O4MR1LPdnx6C2Yn8o9EU3ElOjQuZQvDROjeV+/6GJX2t+1U2wyEFZ mzAQ== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v20si774846oia.159.2019.12.11.01.32.26; Wed, 11 Dec 2019 01:32:38 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728512AbfLKJb7 (ORCPT + 99 others); Wed, 11 Dec 2019 04:31:59 -0500 Received: from mga05.intel.com ([192.55.52.43]:48558 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727829AbfLKJb6 (ORCPT ); Wed, 11 Dec 2019 04:31:58 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2019 01:31:58 -0800 X-IronPort-AV: E=Sophos;i="5.69,301,1571727600"; d="scan'208";a="207613299" Received: from jnikula-mobl3.fi.intel.com (HELO localhost) ([10.237.66.161]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Dec 2019 01:31:54 -0800 From: Jani Nikula To: Stephen Rothwell , Daniel Vetter , Joonas Lahtinen , Rodrigo Vivi , Intel Graphics , DRI Cc: Linux Next Mailing List , Linux Kernel Mailing List , "S\, Maarten Lankhorst" , Qian Cai , Ingo Molnar , Dave Airlie Subject: Re: linux-next: build failure after merge of the drm-intel tree In-Reply-To: <20191210094224.4a294cb7@canb.auug.org.au> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20191210093957.5120f717@canb.auug.org.au> <20191210094224.4a294cb7@canb.auug.org.au> Date: Wed, 11 Dec 2019 11:31:51 +0200 Message-ID: <87a77z4394.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 10 Dec 2019, Stephen Rothwell wrote: > Hi all, > > [Just adding Dave Airlie to the cc list] > > On Tue, 10 Dec 2019 09:39:57 +1100 Stephen Rothwell wrote: >> >> After merging the drm-intel tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: FYI, I've now backmerged drm-next and thus v5.5-rc1 to drm-intel-next-queued, resolving the conflict. BR, Jani. >> >> In file included from include/linux/spinlock_types.h:18, >> from include/linux/mutex.h:16, >> from include/linux/kernfs.h:12, >> from include/linux/sysfs.h:16, >> from include/linux/kobject.h:20, >> from include/linux/of.h:17, >> from include/linux/irqdomain.h:35, >> from include/linux/acpi.h:13, >> from drivers/gpu/drm/i915/i915_drv.c:30: >> drivers/gpu/drm/i915/gem/i915_gem_object.h: In function 'i915_gem_object_pin_pages': >> include/linux/lockdep.h:635:2: error: too many arguments to function 'lock_release' >> 635 | lock_release(&(lock)->dep_map, 0, _THIS_IP_); \ >> | ^~~~~~~~~~~~ >> drivers/gpu/drm/i915/gem/i915_gem_object.h:294:2: note: in expansion of macro 'might_lock_nested' >> 294 | might_lock_nested(&obj->mm.lock, I915_MM_GET_PAGES); >> | ^~~~~~~~~~~~~~~~~ >> include/linux/lockdep.h:352:13: note: declared here >> 352 | extern void lock_release(struct lockdep_map *lock, unsigned long ip); >> | ^~~~~~~~~~~~ >> In file included from include/linux/spinlock_types.h:18, >> from include/linux/spinlock.h:83, >> from include/linux/mmzone.h:8, >> from include/linux/gfp.h:6, >> from include/linux/slab.h:15, >> from drivers/gpu/drm/i915/i915_irq.c:32: >> drivers/gpu/drm/i915/gem/i915_gem_object.h: In function 'i915_gem_object_pin_pages': >> include/linux/lockdep.h:635:2: error: too many arguments to function 'lock_release' >> 635 | lock_release(&(lock)->dep_map, 0, _THIS_IP_); \ >> | ^~~~~~~~~~~~ >> drivers/gpu/drm/i915/gem/i915_gem_object.h:294:2: note: in expansion of macro 'might_lock_nested' >> 294 | might_lock_nested(&obj->mm.lock, I915_MM_GET_PAGES); >> | ^~~~~~~~~~~~~~~~~ >> include/linux/lockdep.h:352:13: note: declared here >> 352 | extern void lock_release(struct lockdep_map *lock, unsigned long ip); >> | ^~~~~~~~~~~~ >> >> Caused by commit >> >> e692b4021a2e ("lockdep: add might_lock_nested()") >> >> interacting with commit >> >> 5facae4f3549 ("locking/lockdep: Remove unused @nested argument from lock_release()") >> >> from Linus' tree. >> >> I have applied the following merge fix patch for today: >> >> From: Stephen Rothwell >> Date: Tue, 10 Dec 2019 09:37:07 +1100 >> Subject: [PATCH] lockdep: fix up for lock_release API change >> >> --- >> include/linux/lockdep.h | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h >> index 5bbfd5866081..664f52c6dd4c 100644 >> --- a/include/linux/lockdep.h >> +++ b/include/linux/lockdep.h >> @@ -632,7 +632,7 @@ do { \ >> typecheck(struct lockdep_map *, &(lock)->dep_map); \ >> lock_acquire(&(lock)->dep_map, subclass, 0, 1, 1, NULL, \ >> _THIS_IP_); \ >> - lock_release(&(lock)->dep_map, 0, _THIS_IP_); \ >> + lock_release(&(lock)->dep_map, _THIS_IP_); \ >> } while (0) >> >> #define lockdep_assert_irqs_enabled() do { \ -- Jani Nikula, Intel Open Source Graphics Center