Re: [PATCH 6/8] rust: add revocable mutex

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Mar 26, 2024 at 07:13:13PM +0100, Danilo Krummrich wrote:
> On Mon, Mar 25, 2024 at 07:22:15PM +0100, Greg KH wrote:
> > On Mon, Mar 25, 2024 at 06:49:10PM +0100, Danilo Krummrich wrote:
> > > From: Wedson Almeida Filho <wedsonaf@gmail.com>
> > > 
> > > This is a mutex where access to its contents can be revoked at runtime.
> > > 
> > > This is different from `Revocable` in a few ways:
> > >   1. The caller may sleep while holding a guard.
> > >   2. Accessors are all serialised.
> > >   3. Accessing is not as cheap (because it involves acquiring the mutex).
> > >   4. The size of the object is larger (because it involves a mutex +
> > >      flag).
> > > 
> > > An example of where this a good fit to be used in device state that
> > > holds registrations to other subsystems.
> > 
> > Why don't we need this in .c files if it is so needed in drivers today?
> 
> You mean revoking access to a resource in general? 

I mean "having a mutex that can be revokable" as you describe here.  Why
is a driver written in rust unique in needing this?

thanks,

greg k-h