From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752358AbdJLAUO (ORCPT ); Wed, 11 Oct 2017 20:20:14 -0400 Received: from ozlabs.org ([103.22.144.67]:42945 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751496AbdJLAUN (ORCPT ); Wed, 11 Oct 2017 20:20:13 -0400 X-powerpc-patch-notification: thanks X-powerpc-patch-commit: 6b2c08f989250c54f31b53dba9ace863a1f3fff6 In-Reply-To: <20171005000430.8080-1-bauerman@linux.vnet.ibm.com> To: Thiago Jung Bauermann , linuxppc-dev@lists.ozlabs.org From: Michael Ellerman Cc: Daniel Black , Thomas Gleixner , linux-kernel@vger.kernel.org, Thiago Jung Bauermann Subject: Re: powerpc: Drop lockdep_assert_cpus_held call from arch_update_cpu_topology Message-Id: <3yCBLz4n8zz9t2Z@ozlabs.org> Date: Thu, 12 Oct 2017 11:20:11 +1100 (AEDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-10-05 at 00:04:30 UTC, Thiago Jung Bauermann wrote: > It turns out that not all paths calling arch_update_cpu_topology hold > cpu_hotplug_lock, but that's ok because those paths aren't supposed to race > with any concurrent hotplug events. > > Callers of arch_update_cpu_topology are expected to know what they are > doing when they call the function without holding the lock, so remove the > lockdep warning. ... > > Signed-off-by: Thiago Jung Bauermann > Fixes: 3e401f7a2e51 ("powerpc: Only obtain cpu_hotplug_lock if called by rtasd") > Link: https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-September/163244.html > Link: https://github.com/linuxppc/linux/issues/106 Applied to powerpc fixes, thanks. https://git.kernel.org/powerpc/c/6b2c08f989250c54f31b53dba9ace8 cheers