On Wed, Sep 25, 2024 at 09:36:10AM +0200, 'Alice Ryhl' via kernel-team wrote:
> On Tue, Sep 24, 2024 at 8:44 PM Carlos Llamas <cmllamas@xxxxxxxxxx> wrote:
> >
> > 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@xxxxxxxxxxxxxxx
> > Signed-off-by: Carlos Llamas <cmllamas@xxxxxxxxxx>
> > ---
> > drivers/android/binder.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> > index d955135ee37a..2be9f3559ed7 100644
> > --- a/drivers/android/binder.c
> > +++ b/drivers/android/binder.c
> > @@ -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;
>
> What about BINDER_WORK_CLEAR_FREEZE_NOTIFICATION?
Oh, you are right! We also need this type here. I haven't played with
the clear notification path just yet (as you can tell). Thanks for
pointing it out though, I'll send a v2.
Looking closer, I see that BINDER_WORK_TRANSACTION_ONEWAY_SPAM_SUSPECT
is also missing, so I'll send a separate patch for that too.
Thanks,
--
Carlos Llamas
