From: syzbot <syzbot+da4f9f61f96525c62cc7@syzkaller.appspotmail.com>
To: amir73il@gmail.com, axboe@kernel.dk, brauner@kernel.org,
dhowells@redhat.com, hch@lst.de, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2)
Date: Fri, 26 Jan 2024 18:28:04 -0800 [thread overview]
Message-ID: <000000000000910cf5060fe42991@google.com> (raw)
In-Reply-To: <000000000000e171200600d6d8bd@google.com>
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()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-01-27 2:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 13:17 [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2) syzbot
2023-12-19 19:43 ` syzbot
2024-01-27 11:46 ` Hillf Danton
2024-01-27 11:57 ` syzbot
2024-01-28 21:43 ` Al Viro
2024-01-29 5:07 ` Hillf Danton
2024-01-28 7:53 ` Hillf Danton
2024-01-28 8:24 ` syzbot
2023-12-20 0:30 ` syzbot
2023-12-20 3:53 ` Amir Goldstein
2023-12-20 4:13 ` syzbot
2024-01-27 2:28 ` syzbot [this message]
2024-01-28 10:11 ` Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000910cf5060fe42991@google.com \
--to=syzbot+da4f9f61f96525c62cc7@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox