From: Miklos Szeredi <miklos@szeredi.hu>
To: syzbot <syzbot+4bdbcaa79e8ee36fe6af@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [syzbot] possible deadlock in iter_file_splice_write (2)
Date: Wed, 28 Jul 2021 16:32:20 +0200 [thread overview]
Message-ID: <CAJfpeguXWAJRyRn=8tLRq41kqjuSnX9VNqNT_V2+jhuttC0nEw@mail.gmail.com> (raw)
In-Reply-To: <00000000000052a12105c82facde@google.com>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
overlayfs-next
next prev parent reply other threads:[~2021-07-28 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 14:19 [syzbot] possible deadlock in iter_file_splice_write (2) syzbot
2021-07-28 14:32 ` Miklos Szeredi [this message]
2021-07-28 20:57 ` syzbot
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='CAJfpeguXWAJRyRn=8tLRq41kqjuSnX9VNqNT_V2+jhuttC0nEw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=syzbot+4bdbcaa79e8ee36fe6af@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).