Re: [syzbot] BUG: MAX_LOCK_DEPTH too low! (3)

[Wen Gu]

On 2022/2/9 4:21 am, syzbot wrote:

> The issue was bisected to:
>
> commit 341adeec9adad0874f29a0a1af35638207352a39
> Author: Wen Gu <guwen@xxxxxxxxxxxxxxxxx>
> Date:   Wed Jan 26 15:33:04 2022 +0000
>
>      net/smc: Forward wakeup to smc socket waitqueue after fallback
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11c2637c700000
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=13c2637c700000
> console output: https://syzkaller.appspot.com/x/log.txt?x=15c2637c700000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+4de3c0e8a263e1e499bc@xxxxxxxxxxxxxxxxxxxxxxxxx
> Fixes: 341adeec9ada ("net/smc: Forward wakeup to smc socket waitqueue after fallback")
>
> BUG: MAX_LOCK_DEPTH too low!
> turning off the locking correctness validator.
> depth: 48  max: 48!

Thanks for syzbot's report.

I will look into this issue and give feedback as soon as possible.

Thanks,
Wen Gu