Re: possible deadlock in f_getown

[syzbot]

syzbot has bisected this issue to:

commit e918188611f073063415f40fae568fa4d86d9044
Author: Boqun Feng <boqun.feng@xxxxxxxxx>
Date:   Fri Aug 7 07:42:20 2020 +0000

    locking: More accurate annotations for read_lock()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=122fe51d500000
start commit:   b6505459 Linux 5.10-rc6
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=112fe51d500000
console output: https://syzkaller.appspot.com/x/log.txt?x=162fe51d500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b3a044ccf5b03ac4
dashboard link: https://syzkaller.appspot.com/bug?extid=8073030e235a5a84dd31
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11b43d79500000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16f2ed79500000

Reported-by: syzbot+8073030e235a5a84dd31@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: e918188611f0 ("locking: More accurate annotations for read_lock()")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection