From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 85FB236AB7D; Thu, 29 Jan 2026 22:29:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769725749; cv=none; b=ucqdaEf/ZzwF7vhykJSs43Z3w4zI5vNoMlPfuts9yoKrlkLUccS11W3ThvEEp9DKqDmmHrbxBWjiwQ4PBBDfIaKnyPBfm22FtxB3SDKPJxZeFM3Mz7nU822OiDx5juXUIuaH8NzdHbUARdtRBhMgTI86ZbDwCfxBoGRoPk+DVhc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769725749; c=relaxed/simple; bh=2rXS3Pzprfsua4VsU6G8SdcDmL3QDI093sbQD1oxjMY=; h=Mime-Version:Content-Type:Date:Message-Id:Cc:To:From:Subject: References:In-Reply-To; b=Ke/xoHpmscLYubp5+SmMwzmMQYxjm4EHEei2Pt/ftraJ8yOKUia0bzERuyoOqR07u7ZDTbUF+/SSzo6MyrqklFVQ2sTurPodhnJp30iZ4EqNDCGpBRPDS+Du2SDBaoGKR3AMT9Nq6b3dQkYNnICm3SXTDMpW129ydUzKsU2pSl0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=UpTNS0PO; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="UpTNS0PO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 20E50C4CEF7; Thu, 29 Jan 2026 22:29:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769725749; bh=2rXS3Pzprfsua4VsU6G8SdcDmL3QDI093sbQD1oxjMY=; h=Date:Cc:To:From:Subject:References:In-Reply-To:From; b=UpTNS0POcvypPCURNqScb3R+hnRiXr3CTJByRH3wWu+A+RO5zDI+2uEfYGbtvVDiM g1HbLqSL8LNeqg/742JKrc4gcM+Qw9MCYQw1wo4M5crsI5V9KTKbjGGVqrXAXrc/f4 TRDOsyOi9c13polScvRTcUb2w3BVB8T88RuGzvPI4u/Pwarn5odWHniuoGbrHu0mL/ ipvMEjJEfjbBpMb7QxG9Ap2BgNEqX2c1KTZmslw7uweBWmDDDA++/r5woSKII3RtyO qJl5h59IvoknOHO215uLjBEL509SM5uNqrZx1ZQ4u1XLikRFHX0kqPetIcrOWmMhKh lAQBvSs9PDi8g== Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 29 Jan 2026 23:29:03 +0100 Message-Id: Cc: "Jason Gunthorpe" , "Bartosz Golaszewski" , "Johan Hovold" , "Greg Kroah-Hartman" , "Rafael J . Wysocki" , "Tzung-Bi Shih" , "Linus Walleij" , "Jonathan Corbet" , "Shuah Khan" , "Wolfram Sang" , "Simona Vetter" , "Dan Williams" , , , , "Bartosz Golaszewski" , , , To: "Laurent Pinchart" From: "Danilo Krummrich" Subject: Re: [PATCH 0/3] Revert "revocable: Revocable resource management" References: <20260124170535.11756-1-johan@kernel.org> <2026012554-chatty-policy-42a1@gregkh> <20260127235232.GS1134360@nvidia.com> <20260129010822.GA3310904@killaraus> In-Reply-To: <20260129010822.GA3310904@killaraus> (Cc: Maxime, Thomas, Maarten) On Thu Jan 29, 2026 at 2:08 AM CET, Laurent Pinchart wrote: > That's what I've been advocating for. The best way to ensure that driver > code will not accessed data freed at .remove() time is to prevent the > code to run at all. With this we are in full agreement, I think that'd be best too. But, I also think that sometimes this isn't possible. For instance, DRM has such a case= with atomic mode setting.