From: Dave Jones <davej@codemonkey.org.uk>
To: Shankara Pailoor <sp3485@columbia.edu>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Andrew Zhu Aday <andrew.aday@columbia.edu>,
syzkaller <syzkaller@googlegroups.com>,
viro@zeniv.linux.org.uk
Subject: Re: WARN_ON_ONCE in fs/iomap.c:993
Date: Mon, 11 Sep 2017 12:46:29 -0400 [thread overview]
Message-ID: <20170911164629.4kuuqgklyelld7am@codemonkey.org.uk> (raw)
In-Reply-To: <CAASgV=ugG=Chc5RK4CK-=FsVm+9UEd-2kSTxQrZFG90bYHpMpw@mail.gmail.com>
On Mon, Sep 11, 2017 at 06:56:05AM -0400, Shankara Pailoor wrote:
> Hi,
>
> I am fuzzing linux 4.13-rc7 with XFS using syzkaller on x86_64 and I
> found the following warning:
>
> WARNING: CPU: 2 PID: 5391 at fs/iomap.c:993 iomap_dio_rw+0xc79/0xe70
>
> Here is a reproducer program: https://pastebin.com/tc014k97
pwrite in one thread, sendfile on another. Same thing trinity has been hitting.
See thread "Subject: Re: iov_iter_pipe warning".
Dave
prev parent reply other threads:[~2017-09-11 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 10:56 WARN_ON_ONCE in fs/iomap.c:993 Shankara Pailoor
2017-09-11 16:46 ` Dave Jones [this message]
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=20170911164629.4kuuqgklyelld7am@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=andrew.aday@columbia.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sp3485@columbia.edu \
--cc=syzkaller@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