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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E7C6C433EF for ; Wed, 16 Feb 2022 07:41:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230330AbiBPHlx (ORCPT ); Wed, 16 Feb 2022 02:41:53 -0500 Received: from gmail-smtp-in.l.google.com ([23.128.96.19]:42456 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230397AbiBPHlu (ORCPT ); Wed, 16 Feb 2022 02:41:50 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1E4D5A653C for ; Tue, 15 Feb 2022 23:41:24 -0800 (PST) Date: Wed, 16 Feb 2022 08:40:45 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1644997246; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uOiuPHiQmy5b8Qczc4D0Y+cV4Dyd9l37rqefvPeQyok=; b=y54hTjD3laosXu6abNeyuj9xM7XS/ixeG4dSr7/uctB5IbmWYV680ueR2/wrBFo76BQqeq e/3qxH7PKjdkreYb0GUpJF7c4kVVa4JRU7DxyDIOyrdCeihXFNNp8VVWdZq/REl5wOQbvw 1OLBgQUnUZ2dNtlze9GrWbv3YNM3WrC/hTIxyL9LbtNTEIDxi17mpMlqxyXnttPjn2kLoC w240d/HUEcB0L9SLNC5dV3NsoWhXfm+fr3kiPkYuU6fGGfprgxdbi0lWFRYAw4hLzlyxyq EtFUiotS8TVFTFJHGVrGOkjAFXrRl7lzwHSiP8ZQiIShT+Ca9Fc3BdiVFvByiw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1644997246; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uOiuPHiQmy5b8Qczc4D0Y+cV4Dyd9l37rqefvPeQyok=; b=IKADsweeCveWUCuSN4KuISDViGfqpDJ95GXtfVROgz4KKgFd7wwQraQ0KHw3u9Tlkvrv9P 9hAzJrvl7nXNufAg== From: Sebastian Siewior To: Jiri Kosina Cc: John Ogness , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] drm: fb-helper: Avoid nesting spinlock_t into raw_spinlock_t Message-ID: References: <87o8382j5s.fsf@jogness.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022-02-15 20:59:24 [+0100], Jiri Kosina wrote: > Thanks for confirmation, seems like this problem is indeed cured by your > series. Oki. > I still believe though that we shouldn't let 5.17 released with this > warning being emitted into dmesg, so I'd suggest going with my patch for > mainline, and revert it in your series on top of it. No. That warning is only visible with CONFIG_PROVE_RAW_LOCK_NESTING with the following paragraph in its help: | NOTE: There are known nesting problems. So if you enable this | option expect lockdep splats until these problems have been fully | addressed which is work in progress. This config switch allows to | identify and analyze these problems. It will be removed and the | check permanently enabled once the main issues have been fixed. This warning in this call chain should affect every console driver which acquires a lock. > Thanks, Sebastian