From: Waiman Long <longman@redhat.com>
To: botta633 <bottaawesome633@gmail.com>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
linux-ext4@vger.kernel.org, syzkaller@googlegroups.com,
syzbot+7f4a6f7f7051474e40ad@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ext4: Forcing subclasses to have same name pointer as their parent class
Date: Sun, 14 Jul 2024 17:22:21 -0400 [thread overview]
Message-ID: <fff79c2a-d659-4faa-83e2-e36c2e2bda2b@redhat.com> (raw)
In-Reply-To: <20240714051427.114044-1-bottaawesome633@gmail.com>
On 7/14/24 01:14, botta633 wrote:
> From: Ahmed Ehab <bottaawesome633@gmail.com>
>
> Preventing lockdep_set_subclass from creating a new instance of the
> string literal. Hence, we will always have the same class->name among
> parent and subclasses. This prevents kernel panics when looking up a
> lock class while comparing class locks and class names.
>
> Reported-by: <syzbot+7f4a6f7f7051474e40ad@syzkaller.appspotmail.com>
> Fixes: fd5e3f5fe27
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Ahmed Ehab <bottaawesome633@gmail.com>
> ---
> include/linux/lockdep.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h
> index 08b0d1d9d78b..df8fa5929de7 100644
> --- a/include/linux/lockdep.h
> +++ b/include/linux/lockdep.h
> @@ -173,7 +173,7 @@ static inline void lockdep_init_map(struct lockdep_map *lock, const char *name,
> (lock)->dep_map.lock_type)
>
> #define lockdep_set_subclass(lock, sub) \
> - lockdep_init_map_type(&(lock)->dep_map, #lock, (lock)->dep_map.key, sub,\
> + lockdep_init_map_type(&(lock)->dep_map, (lock)->dep_map.name, (lock)->dep_map.key, sub,\
> (lock)->dep_map.wait_type_inner, \
> (lock)->dep_map.wait_type_outer, \
> (lock)->dep_map.lock_type)
ext4 is a filesystem. It has nothing to do with locking/lockdep. Could
you resend the patches with the proper prefix of "lockdep:" or
"locking/lockdep:"?
Thanks,
Longman
next prev parent reply other threads:[~2024-07-14 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 5:14 [PATCH v2 1/2] ext4: Forcing subclasses to have same name pointer as their parent class botta633
2024-07-14 5:14 ` [PATCH 2/2] ext4: Testing lock class and subclass got the same name pointer botta633
2024-07-14 22:00 ` Boqun Feng
2024-07-14 21:22 ` Waiman Long [this message]
[not found] ` <CA+6bSasRZ7HRURZcSPEsAyDtNDdx+7UGwuXRG+Dw0Gqo+vs9Ew@mail.gmail.com>
2024-07-14 21:41 ` [PATCH v2 1/2] ext4: Forcing subclasses to have same name pointer as their parent class Boqun Feng
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=fff79c2a-d659-4faa-83e2-e36c2e2bda2b@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=bottaawesome633@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+7f4a6f7f7051474e40ad@syzkaller.appspotmail.com \
--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