mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boqun Feng <boqun@kernel.org>
To: "Onur Özkan" <work@onurozkan.dev>
Cc: rust-for-linux@vger.kernel.org, lossin@kernel.org,
	lyude@redhat.com, ojeda@kernel.org, alex.gaynor@gmail.com,
	boqun.feng@gmail.com, gary@garyguo.net, a.hindborg@kernel.org,
	aliceryhl@google.com, tmgross@umich.edu, dakr@kernel.org,
	peterz@infradead.org, mingo@redhat.com, will@kernel.org,
	longman@redhat.com, felipe_life@live.com, daniel@sedlak.dev,
	daniel.almeida@collabora.com, thomas.hellstrom@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 2/7] ww_mutex: add ww_class field unconditionally
Date: Wed, 23 Sep 2026 07:34:22 +0200	[thread overview]
Message-ID: <arNk3mN8Uq9cU5bz@MacBook-0RXW5> (raw)
In-Reply-To: <20260102175302.194435-3-work@onurozkan.dev>

On Fri, Jan 02, 2026 at 08:52:57PM +0300, Onur Özkan wrote:
> Removes DEBUG_WW_MUTEXES guard around the ww_class field
> in struct ww_mutex and struct ww_acquire_ctx to always
> initialize it.
> 
> Keeping the class pointer available unconditionally allows
> Rust abstractions to keep from_raw() simple on Mutex and
> AcquireCtx, simplify AcquireCtx reinitialization logic and
> validate Mutex and AcquireCtx class pairing in much simpler way.
> 

@Peter and @Waiman, any dispute on this patch? I would like to make some
progress on this since it'll be needed for GPUVM and KMS if I understand
correctly.

Regards,
Boqun

> Link: https://lore.kernel.org/all/ECC0425A-8B18-4626-8EA8-2F843C45E0A1@collabora.com/
> Signed-off-by: Onur Özkan <work@onurozkan.dev>
> ---
>  include/linux/ww_mutex.h | 8 ++------
>  1 file changed, 2 insertions(+), 6 deletions(-)
> 
> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
> index 45ff6f7a872b..c9835035b6d6 100644
> --- a/include/linux/ww_mutex.h
> +++ b/include/linux/ww_mutex.h
> @@ -47,9 +47,7 @@ struct ww_class {
>  struct ww_mutex {
>  	struct WW_MUTEX_BASE base;
>  	struct ww_acquire_ctx *ctx;
> -#ifdef DEBUG_WW_MUTEXES
>  	struct ww_class *ww_class;
> -#endif
>  };
>  
>  struct ww_acquire_ctx {
> @@ -58,9 +56,9 @@ struct ww_acquire_ctx {
>  	unsigned int acquired;
>  	unsigned short wounded;
>  	unsigned short is_wait_die;
> +	struct ww_class *ww_class;
>  #ifdef DEBUG_WW_MUTEXES
>  	unsigned int done_acquire;
> -	struct ww_class *ww_class;
>  	void *contending_lock;
>  #endif
>  #ifdef CONFIG_DEBUG_LOCK_ALLOC
> @@ -110,9 +108,7 @@ static inline void ww_mutex_init(struct ww_mutex *lock,
>  {
>  	ww_mutex_base_init(&lock->base, ww_class->mutex_name, &ww_class->mutex_key);
>  	lock->ctx = NULL;
> -#ifdef DEBUG_WW_MUTEXES
>  	lock->ww_class = ww_class;
> -#endif
>  }
>  
>  /**
> @@ -147,8 +143,8 @@ static inline void ww_acquire_init(struct ww_acquire_ctx *ctx,
>  	ctx->acquired = 0;
>  	ctx->wounded = false;
>  	ctx->is_wait_die = ww_class->is_wait_die;
> -#ifdef DEBUG_WW_MUTEXES
>  	ctx->ww_class = ww_class;
> +#ifdef DEBUG_WW_MUTEXES
>  	ctx->done_acquire = 0;
>  	ctx->contending_lock = NULL;
>  #endif
> -- 
> 2.51.2
> 

  reply	other threads:[~2026-09-23  5:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 17:52 [PATCH v9 0/7] rust: add ww_mutex support Onur Özkan
2026-01-02 17:52 ` [PATCH v9 1/7] rust: add C wrappers for ww_mutex inline functions Onur Özkan
2026-01-02 17:52 ` [PATCH v9 2/7] ww_mutex: add ww_class field unconditionally Onur Özkan
2026-09-23  5:34   ` Boqun Feng [this message]
2026-01-02 17:52 ` [PATCH v9 3/7] rust: error: add EDEADLK Onur Özkan
2026-01-02 20:27   ` Onur Özkan
2026-01-02 17:52 ` [PATCH v9 4/7] rust: implement Class for ww_class support Onur Özkan
2026-01-02 17:53 ` [PATCH v9 5/7] rust: ww_mutex: add Mutex, AcquireCtx and MutexGuard Onur Özkan
2026-01-03  5:40   ` kernel test robot
2026-09-22  8:54   ` Boqun Feng
2026-09-23  3:48     ` Onur Özkan
2026-09-23  5:32       ` Boqun Feng
2026-09-25  8:56         ` Onur Özkan
2026-01-02 17:53 ` [PATCH v9 6/7] rust: ww_mutex: implement LockSet Onur Özkan
2026-01-02 17:53 ` [PATCH v9 7/7] MAINTAINERS: add Onur Özkan as WW MUTEX maintainer Onur Özkan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=arNk3mN8Uq9cU5bz@MacBook-0RXW5 \
    --to=boqun@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=daniel@sedlak.dev \
    --cc=felipe_life@live.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=mingo@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tmgross@umich.edu \
    --cc=will@kernel.org \
    --cc=work@onurozkan.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®