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 18D66C636D4 for ; Mon, 13 Feb 2023 18:06:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229557AbjBMSG4 (ORCPT ); Mon, 13 Feb 2023 13:06:56 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52370 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229720AbjBMSGx (ORCPT ); Mon, 13 Feb 2023 13:06:53 -0500 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id E6DFBA5D1 for ; Mon, 13 Feb 2023 10:06:28 -0800 (PST) Received: (qmail 916650 invoked by uid 1000); 13 Feb 2023 13:05:48 -0500 Date: Mon, 13 Feb 2023 13:05:48 -0500 From: Alan Stern To: Greg Kroah-Hartman Cc: Peter Zijlstra , Tetsuo Handa , syzkaller , Dmitry Vyukov , "Rafael J. Wysocki" , Ingo Molnar , Boqun Feng , LKML , USB list , Linus Torvalds , Hillf Danton Subject: Re: [PATCH RFC] drivers/core: Replace lockdep_set_novalidate_class() with unique class keys Message-ID: References: <20230208080739.1649-1-hdanton@sina.com> <1ad499bb-0c53-7529-ff00-e4328823f6fa@I-love.SAKURA.ne.jp> <52c7d509-ba9e-a121-60c9-138d7ff3f667@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 13, 2023 at 06:51:57PM +0100, Greg Kroah-Hartman wrote: > But back to the original issue here, why any of this? What's wrong with > what we have now? I haven't seen real locking issues reported yet (only > odd syzbot reports that didn't make any sense.) Is this effort even > worth it? A large part of the reason those syzbot reports didn't make any sense was because they didn't include any lockdep information. Making lockdep aware of device locking would make those reports a lot easier to understand and would help with fixing the bugs. And it might even help with catching similar problems before they get merged into the kernel. Will it be worthwhile in the end? I have no idea. Alan Stern