public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Ahmed Ehab <bottaawesome633@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	linux-ext4@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: [PATCH v8 2/2] locking/lockdep: Test no new string literal is created in lockdep_set_subclass()
Date: Tue, 10 Sep 2024 02:47:26 -0700	[thread overview]
Message-ID: <ZuAVrkMQvk41PNKH@boqun-archlinux> (raw)
In-Reply-To: <20240905011220.356973-1-bottaawesome633@gmail.com>

Hi Ahmed,

On Thu, Sep 05, 2024 at 04:12:20AM +0300, Ahmed Ehab wrote:
> Add a test case to ensure that no new name string literal will be
> created in lockdep_set_subclass(), otherwise a warning will be triggered
> in look_up_lock_class(). Add this to catch the problem in the future. 
> 

This overall looks good to me, I'm going to take it and create a PR for
tip in next release. However, please note a few things:

* Since you only send one of the patch from your original series, you
  should avoid use "2/2" in the title, because it could be confusing
  whether there is "1/2" lost in sending. If you want to make sure
  people aware that this is a continued work of the patch #2 in your
  original series, you can put some description after the following
  "---"

* You need also to put changes between patch versions after "---" so
  that people can know the context, for example, I have no idea why you
  send a v8 after v7 and what's the delta here. Here is an example of
  how to document the delta:

  	https://lore.kernel.org/rust-for-linux/20240827-static-mutex-v2-1-17fc32b20332@google.com/

Regards,
Boqun

> Signed-off-by: Ahmed Ehab <bottaawesome633@gmail.com>
> ---
>  lib/locking-selftest.c | 40 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
> 
> diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c
> index 6f6a5fc85b42..0783ee97c971 100644
> --- a/lib/locking-selftest.c
> +++ b/lib/locking-selftest.c
> @@ -2710,6 +2710,44 @@ static void local_lock_3B(void)
>  
>  }
>  
> +#if CONFIG_DEBUG_LOCK_ALLOC
> +static inline const char *rw_semaphore_lockdep_name(struct rw_semaphore *rwsem)
> +{
> +	return rwsem->dep_map.name;
> +}
> +#else
> +static inline const char *rw_semaphore_lockdep_name(struct rw_semaphore *rwsem)
> +{
> +	return NULL;
> +}
> +#endif
> +
> +static void lock_class_subclass_X1(void)
> +{
> +	const char *name_before_setting_subclass = rw_semaphore_lockdep_name(&rwsem_X1);
> +	const char *name_after_setting_subclass;
> +
> +	lockdep_set_subclass(&rwsem_X1, 1);
> +	name_after_setting_subclass = rw_semaphore_lockdep_name(&rwsem_X1);
> +	DEBUG_LOCKS_WARN_ON(name_before_setting_subclass != name_after_setting_subclass);
> +}
> +
> +/*
> + * after setting the subclass the lockdep_map.name changes
> + * if we initialize a new string literal for the subclass
> + * we will have a new name pointer
> + */
> +static void class_subclass_X1_name_test(void)
> +{
> +	printk("  --------------------------------------------------------------------------\n");
> +	printk("  | class and subclass name test|\n");
> +	printk("  ---------------------\n");
> +
> +	print_testname("lock class and subclass same name");
> +	dotest(lock_class_subclass_X1, SUCCESS, LOCKTYPE_RWSEM);
> +	pr_cont("\n");
> +}
> +
>  static void local_lock_tests(void)
>  {
>  	printk("  --------------------------------------------------------------------------\n");
> @@ -2920,6 +2958,8 @@ void locking_selftest(void)
>  	dotest(hardirq_deadlock_softirq_not_deadlock, FAILURE, LOCKTYPE_SPECIAL);
>  	pr_cont("\n");
>  
> +	class_subclass_X1_name_test();
> +
>  	if (unexpected_testcase_failures) {
>  		printk("-----------------------------------------------------------------\n");
>  		debug_locks = 0;
> -- 
> 2.46.0
> 

      reply	other threads:[~2024-09-10  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  1:12 [PATCH v8 2/2] locking/lockdep: Test no new string literal is created in lockdep_set_subclass() Ahmed Ehab
2024-09-10  9:47 ` Boqun Feng [this message]

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=ZuAVrkMQvk41PNKH@boqun-archlinux \
    --to=boqun.feng@gmail.com \
    --cc=bottaawesome633@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller@googlegroups.com \
    --cc=will@kernel.org \
    /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