Re: New panic in main-n253273-a52d8d4a6c6:

From: Rob Wing <rob.fx907_at_gmail.com>
Date: Tue, 22 Feb 2022 01:47:46 UTC
kinda thinking this might be related to commit f40dd6c8034b ("tty: switch
ttyhook_register to use fget_cap_locked")

fget_unlocked() must have grabbed an extra reference count on the file
pointer that fget_cap_locked() doesn't get

On Mon, Feb 21, 2022 at 4:35 PM Hans Petter Selasky <hps@selasky.org> wrote:

> On 2/22/22 00:42, Michael Jung wrote:
> > Hi:
> >
> > I was trying to remember what I did that was odd when this crash
> occurred then it
> > hit me.  You can repeat this panic by doing:
> >
> > # watch -I -W pts/0
> >
> > Here is another panic that happened write after issuing "watch" for
> comparison.
> >
> > http://mail.mikej.com/core.txt.1
> >
> > http://mail.mikej.com/info.1
> >
> > http://mail.mikej.com/vmcore.1
> >
>
> I also need your kernel and debug kernel to fully debug this.
>
> 1) Do ssh to machine.
> 2) watch -i -W pts/0 (does not panic over here)
>
> Can you explain what step 1 is? An scp ?
>
> Refcount is -1.
> f_count = 0xffffffff
>
> f_data = 0xfffff800158b0400
>
> In your KGDB, can you enter:
>
> info 0xffffffff81b052d0
>
> Does the attached patch make any difference?
>
> --HPS