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 056C2C71155 for ; Fri, 18 Aug 2023 15:56:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378347AbjHRP41 (ORCPT ); Fri, 18 Aug 2023 11:56:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53276 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1378438AbjHRP4Y (ORCPT ); Fri, 18 Aug 2023 11:56:24 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3CD5D2722 for ; Fri, 18 Aug 2023 08:56:23 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id D50C11F8AC; Fri, 18 Aug 2023 15:56:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1692374181; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ck7ckU+/gf4JNt8Ash+l5BzHSiiOBGSDD7RN1DViGuc=; b=xUUI8Jy2qVLDxk2Yw2zOCL3/NoCJwsU9ZzCz2YbFQhpbMUFcIdW+xRr6TIGKYQbtEtBcF5 UmVOc86eTAqtXrx57kAf1sx2FmN/DDmu6qKcvvJVIBrbhLdhFES9kqMTLomCpD2d7yOrrU 3x3835OVhOIEirjRygYLE6ygekxkha4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1692374181; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ck7ckU+/gf4JNt8Ash+l5BzHSiiOBGSDD7RN1DViGuc=; b=MqAQxNBbpshhWYUCKYeVoIwqCDc650X0W4PmPQ97gUkfa2xi1xyghgdHMbEhsbUG/VrfBS SxtaCxvDN0Rm/wBQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 8DAED13441; Fri, 18 Aug 2023 15:56:21 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id uWVpIaWU32RAbQAAMHmgww (envelope-from ); Fri, 18 Aug 2023 15:56:21 +0000 Date: Fri, 18 Aug 2023 17:56:20 +0200 From: Joerg Roedel To: Jason Gunthorpe Cc: Marek Szyprowski , iommu@lists.linux.dev, Joerg Roedel , Len Brown , linux-acpi@vger.kernel.org, "Rafael J. Wysocki" , Robin Murphy , Will Deacon , Lu Baolu , Kevin Tian , Chen-Yu Tsai Subject: Re: [PATCH v2 0/4] Fix device_lock deadlock on two probe() paths Message-ID: References: <0-v2-d2762acaf50a+16d-iommu_group_locking2_jgg@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Thu, Aug 17, 2023 at 03:33:16PM -0300, Jason Gunthorpe wrote: > Bascially.. Yikes! Hmm, that is a difficult situation. Even if the problem is a misuse of the APIs we can not just blindly break other drivers by our core changes. We need to resolve this situation pretty soon, otherwise I need to remove the locking rework patches from the IOMMU tree until the callers are fixed. Is there a way to keep the broken drivers working for now? Regards, -- Jörg Rödel jroedel@suse.de SUSE Software Solutions Germany GmbH Frankenstraße 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman