lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Sep 2021 13:20:00 -0400
From:   Desmond Cheong Zhi Xi <>
To:     syzbot <>,,,,,,,,,,,
Subject: Re: [syzbot] possible deadlock in f_getown

On 23/9/21 2:03 am, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> commit f671a691e299f58835d4660d642582bf0e8f6fda
> Author: Desmond Cheong Zhi Xi <>
> Date:   Fri Jul 2 09:18:30 2021 +0000
>      fcntl: fix potential deadlocks for &fown_struct.lock
> bisection log:
> start commit:   293837b9ac8d Revert "i915: fix remap_io_sg to verify the p..
> git tree:       upstream
> kernel config:
> dashboard link:
> syz repro:
> C reproducer:
> If the result looks correct, please mark the issue as fixed by replying with:
> #syz fix: fcntl: fix potential deadlocks for &fown_struct.lock
> For information about bisection process see:

#syz fix: fcntl: fix potential deadlocks for &fown_struct.lock

Think I got jumbled a bit when marking the dups. This bug shares the 
same root cause as [1], and is fixed by the same patch. Nice that Syzbot 

Link: [1]

Powered by blists - more mailing lists