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 E6AB633D6E6; Fri, 16 Jan 2026 16:41:52 +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=1768581713; cv=none; b=TgO1BRtBajJhlrezKy9USz31+Wv9lLF35LBsv4vW2e0NNzyyrSJheLGL7mSd5Ro0FGeXvkHb8U66WSm03iAPlCnBt8TimefWNhK2aaRIXRY/zeEwv55Ygv4Az8Tfk5zTu8w8BXS16UZgMgX5mMj0BLkcGy3dYYJOt7Arf50eaNw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768581713; c=relaxed/simple; bh=UUqsgyZascW9bL55SH5mw94V3XSsw2UiZr6S63xzoYA=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=lITu3Fw2DJsvX/7sxAmZL0gBw7fJDMMTUL7obDTTZK8pl6KGCA8y16IUXIU1T/E3Y3ilPj3x3PRWdO/A15NkVBXtBUdYUiyPZF4v3I7/vk6AvE7UelzghAoMqmfUF/LZwZqMC0SHtPoPhN0LxgKtZFs4+YZItvRr9QuyTKLSecY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=XHMRLvhP; 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="XHMRLvhP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1F39BC116C6; Fri, 16 Jan 2026 16:41:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768581712; bh=UUqsgyZascW9bL55SH5mw94V3XSsw2UiZr6S63xzoYA=; h=Date:Subject:Cc:To:From:References:In-Reply-To:From; b=XHMRLvhPQj36KWKO5o1RPd/7s2L9jUMDDoaR1A2L7wgHeWqlYEizLi1AkhWkbjaGQ +BNVwgTm4ffeTtpP4nLGkTQCB6ltcNySeT9eAmZNMjUEK3xq2Bfq2vsjzOPIfRO1Gu F4aICMFfXTt4Nf1cNBlg1Ob4O667jWcaDFoEFr+/0bk8Tz14W9Tpb+xXo0LGOQJccQ VLRWeguQFSi+1zhiWeLpYLJwZkzJBHTYstgrM4BGWcSeStpqw+zMTAXsmY4rjoisja WFJeW1TeECHBgbTSFnpooblKQy6Y/ZO7O+63gXueNIvKjTvgkmKMGEMb1AxfWpLPOV Xsq+pGGjhi4dA== Precedence: bulk X-Mailing-List: linux-gpio@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: Fri, 16 Jan 2026 17:41:47 +0100 Message-Id: Subject: Re: [PATCH v7 1/3] revocable: Revocable resource management Cc: "Bartosz Golaszewski" , "Tzung-Bi Shih" , "Benson Leung" , "Greg Kroah-Hartman" , "Rafael J . Wysocki" , "Linus Walleij" , "Jonathan Corbet" , "Shuah Khan" , , , , , "Wolfram Sang" , "Simona Vetter" , "Dan Williams" , "Jason Gunthorpe" , To: "Laurent Pinchart" From: "Danilo Krummrich" References: <20260116080235.350305-1-tzungbi@kernel.org> <20260116080235.350305-2-tzungbi@kernel.org> <20260116160424.GA14499@pendragon.ideasonboard.com> In-Reply-To: <20260116160424.GA14499@pendragon.ideasonboard.com> On Fri Jan 16, 2026 at 5:04 PM CET, Laurent Pinchart wrote: > Based on the discussions we had at LPC, the revocable resource management= API > is not the right solution to handle races between device removal and user= space > access. Please see: https://lore.kernel.org/all/DFQ5D44A0348.PZJIGPL972N@kernel.org= / > It is however a possibly useful tool for races between producers and cons= umers > *inside the kernel*. Do you have an example for such a case?