[syzbot] possible deadlock in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    d1dc87763f40 assoc_array: Fix BUG_ON during garbage collect
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=125e36ebf00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e652a1bc921d8948
dashboard link: https://syzkaller.appspot.com/bug?extid=5c3c53e6db862466e7b6
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=141cc87df00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12613edbf00000

Bisection is inconclusive: the issue happens on the oldest tested release.

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1679bfcbf00000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1579bfcbf00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1179bfcbf00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c3c53e6db862466e7b6@xxxxxxxxxxxxxxxxxxxxxxxxx

=====================================================
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.18.0-syzkaller-11972-gd1dc87763f40 #0 Not tainted
-----------------------------------------------------
syz-executor227/3609 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
ffff88801b5aa0c0 (&new->fa_lock){....}-{2:2}, at: 


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches