From: Christoph Hellwig <hch@lst.de>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@fb.com>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
chandan <chandan@linux.vnet.ibm.com>
Subject: Re: [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at fs/iomap.c:993
Date: Mon, 18 Sep 2017 17:27:06 +0200 [thread overview]
Message-ID: <20170918152706.GA11482@lst.de> (raw)
In-Reply-To: <1505746565.6990.18.camel@abdul.in.ibm.com>
On Mon, Sep 18, 2017 at 08:26:05PM +0530, Abdul Haleem wrote:
> Hi,
>
> A warning is triggered from:
>
> file fs/iomap.c in function iomap_dio_rw
>
> if (ret)
> goto out_free_dio;
>
> ret = invalidate_inode_pages2_range(mapping,
> start >> PAGE_SHIFT, end >> PAGE_SHIFT);
> >> WARN_ON_ONCE(ret);
> ret = 0;
>
> inode_dio_begin(inode);
This is expected and an indication of a problematic workload - which
may be triggered by a fuzzer.
next prev parent reply other threads:[~2017-09-18 15:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:56 [linux-next][XFS][trinity] WARNING: CPU: 32 PID: 31369 at fs/iomap.c:993 Abdul Haleem
2017-09-18 15:27 ` Christoph Hellwig [this message]
2017-09-18 15:28 ` [XFS][trinity] " Jens Axboe
2017-09-18 15:28 ` [linux-next][XFS][trinity] " Jens Axboe
2017-09-18 15:39 ` [XFS][trinity] " Christoph Hellwig
2017-09-18 15:39 ` [linux-next][XFS][trinity] " Christoph Hellwig
2017-09-18 15:43 ` Al Viro
2017-09-18 15:51 ` [XFS][trinity] " Jens Axboe
2017-09-18 15:51 ` [linux-next][XFS][trinity] " Jens Axboe
2017-09-18 21:53 ` Dave Chinner
2017-09-18 21:31 ` Dave Chinner
2017-09-18 22:00 ` Eric Sandeen
2017-09-18 22:04 ` [XFS][trinity] " Darrick J. Wong
2017-09-18 22:04 ` [linux-next][XFS][trinity] " Darrick J. Wong
2017-09-18 22:05 ` Dave Chinner
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=20170918152706.GA11482@lst.de \
--to=hch@lst.de \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=axboe@fb.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.