]> git.ipfire.org Git - thirdparty/kernel/linux.git/commitdiff
binder: fix BINDER_WORK_FROZEN_BINDER debug logs
authorCarlos Llamas <cmllamas@google.com>
Thu, 26 Sep 2024 23:36:15 +0000 (23:36 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 13 Oct 2024 15:12:21 +0000 (17:12 +0200)
The BINDER_WORK_FROZEN_BINDER type is not handled in the binder_logs
entries and it shows up as "unknown work" when logged:

  proc 649
  context binder-test
    thread 649: l 00 need_return 0 tr 0
    ref 13: desc 1 node 8 s 1 w 0 d 0000000053c4c0c3
    unknown work: type 10

This patch add the freeze work type and is now logged as such:

  proc 637
  context binder-test
    thread 637: l 00 need_return 0 tr 0
    ref 8: desc 1 node 3 s 1 w 0 d 00000000dc39e9c6
    has frozen binder

Fixes: d579b04a52a1 ("binder: frozen notification")
Cc: stable@vger.kernel.org
Acked-by: Todd Kjos <tkjos@google.com>
Signed-off-by: Carlos Llamas <cmllamas@google.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Link: https://lore.kernel.org/r/20240926233632.821189-5-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/android/binder.c

index d955135ee37a1aefa3b0049a4b9374cb78e971c2..2be9f3559ed79c91180c5e68dabc98d77a550a26 100644 (file)
@@ -6408,6 +6408,9 @@ static void print_binder_work_ilocked(struct seq_file *m,
        case BINDER_WORK_CLEAR_DEATH_NOTIFICATION:
                seq_printf(m, "%shas cleared death notification\n", prefix);
                break;
+       case BINDER_WORK_FROZEN_BINDER:
+               seq_printf(m, "%shas frozen binder\n", prefix);
+               break;
        default:
                seq_printf(m, "%sunknown work: type %d\n", prefix, w->type);
                break;