Files
linux-stable-mirror/include/linux
Ahmed Ehab 48c3352453 locking/lockdep: Avoid creating new name string literals in lockdep_set_subclass()
commit d7fe143cb1 upstream.

Syzbot reports a problem that a warning will be triggered while
searching a lock class in look_up_lock_class().

The cause of the issue is that a new name is created and used by
lockdep_set_subclass() instead of using the existing one. This results
in a lock instance has a different name pointer than previous registered
one stored in lock class, and WARN_ONCE() is triggered because of that
in look_up_lock_class().

To fix this, change lockdep_set_subclass() to use the existing name
instead of a new one. Hence, no new name will be created by
lockdep_set_subclass(). Hence, the warning is avoided.

[boqun: Reword the commit log to state the correct issue]

Reported-by: <syzbot+7f4a6f7f7051474e40ad@syzkaller.appspotmail.com>
Fixes: de8f5e4f2d ("lockdep: Introduce wait-type checks")
Cc: stable@vger.kernel.org
Signed-off-by: Ahmed Ehab <bottaawesome633@gmail.com>
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
Link: https://lore.kernel.org/lkml/20240824221031.7751-1-bottaawesome633@gmail.com/
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2024-12-14 19:51:14 +01:00
..
2023-07-23 13:46:54 +02:00
2024-01-25 14:52:51 -08:00
2024-07-05 09:14:50 +02:00
2023-12-20 15:17:37 +01:00
2023-03-30 12:47:50 +02:00
2024-04-10 16:19:07 +02:00
2024-04-10 16:18:55 +02:00
2023-11-20 11:08:16 +01:00
2024-04-10 16:19:00 +02:00
2023-08-26 14:23:39 +02:00
2024-01-25 14:52:33 -08:00
2024-06-16 13:39:27 +02:00
2023-11-28 16:56:21 +00:00
2023-10-19 23:05:33 +02:00
2023-10-19 23:05:33 +02:00
2023-12-13 18:36:35 +01:00
2024-10-17 15:11:06 +02:00