lkml.org 
[lkml]   [2024]   [Jan]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2)
On Sat, Jan 27, 2024 at 4:28 AM syzbot
<syzbot+da4f9f61f96525c62cc7@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit da40448ce4eb4de18eb7b0db61dddece32677939
> Author: Amir Goldstein <amir73il@gmail.com>
> Date: Thu Nov 30 14:16:23 2023 +0000
>
> fs: move file_start_write() into direct_splice_actor()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=105aa1a0180000
> start commit: 2cf4f94d8e86 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e5751b3a2226135d
> dashboard link: https://syzkaller.appspot.com/bug?extid=da4f9f61f96525c62cc7
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176a4f49e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154aa8d6e80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: fs: move file_start_write() into direct_splice_actor()

Yes. I already wrote that this work is going to fix this repro
as well as other potential deadlocks.

#syz fix: fs: move file_start_write() into direct_splice_actor()

Thanks,
Amir.

\
 
 \ /
  Last update: 2024-05-27 14:37    [W:0.151 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site