linux-kernel - Re: [syzbot] [overlayfs?] possible deadlock in seq_read

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <CAOQ4uxg-nL69cbs8J4xmOd=EAQTiB-cfWgZR0TvY+hb144nZSA@mail.gmail.com>
Date: Sun, 28 Jan 2024 12:11:58 +0200
From: Amir Goldstein <amir73il@...il.com>
To: syzbot <syzbot+da4f9f61f96525c62cc7@...kaller.appspotmail.com>
Cc: axboe@...nel.dk, brauner@...nel.org, dhowells@...hat.com, hch@....de, 
	jack@...e.cz, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-unionfs@...r.kernel.org, miklos@...redi.hu, rafael@...nel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2)

On Sat, Jan 27, 2024 at 4:28 AM syzbot
<syzbot+da4f9f61f96525c62cc7@...kaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit da40448ce4eb4de18eb7b0db61dddece32677939
> Author: Amir Goldstein <amir73il@...il.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.