linux-kernel - Re: [PATCH v5 3/4] sample: rust_misc_device: Demonstrate additional get/set value functionality

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241206130449.GC7684@google.com>
Date: Fri, 6 Dec 2024 13:04:49 +0000
From: Lee Jones <lee@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, arnd@...db.de, ojeda@...nel.org,
	alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net,
	bjorn3_gh@...tonmail.com, benno.lossin@...ton.me,
	a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu,
	rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v5 3/4] sample: rust_misc_device: Demonstrate additional
 get/set value functionality

On Fri, 06 Dec 2024, Greg KH wrote:

> On Fri, Dec 06, 2024 at 12:42:14PM +0000, Lee Jones wrote:
> > Expand the complexity of the sample driver by providing the ability to
> > get and set an integer.  The value is protected by a mutex.
> > 
> > Here is a simple userspace program that fully exercises the sample
> > driver's capabilities.
> 
> nit, subject line should have "samples" not "sample" :)

Ack.

> > +    fn get_value(&self, mut writer: UserSliceWriter) -> Result<isize> {
> > +        let guard = self.inner.lock();
> > +        let value = guard.value;
> > +
> > +        // Refrain from calling write() on a locked resource
> > +        drop(guard);
> > +
> > +        pr_info!("-> Copying data to userspace (value: {})\n", &value);
> > +
> > +        writer.write::<i32>(&value)?;
> > +        Ok(0)
> > +    }
> 
> I don't understand why you have to drop the mutex before calling
> pr_info() and write (i.e. copy_to_user())?  It's a mutex, not a
> spinlock, so you can hold it over that potentially-sleeping call, right?
> Or is there some other reason why here?

This was a request from Alice to demonstrate how to unlock a mutex.

-- 
Lee Jones [李琼斯]