From: Al Viro <viro@ZenIV•linux.org.uk>
To: Christoph Hellwig <hch@lst•de>
Cc: Jens Axboe <axboe@kernel•dk>,
Abdul Haleem <abdhalee@linux•vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
linux-xfs <linux-xfs@vger•kernel.org>,
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 16:43:29 +0100 [thread overview]
Message-ID: <20170918154328.GA32076@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20170918153947.GA12635@lst.de>
On Mon, Sep 18, 2017 at 05:39:47PM +0200, Christoph Hellwig wrote:
> On Mon, Sep 18, 2017 at 09:28:55AM -0600, Jens Axboe wrote:
> > If it's expected, why don't we kill the WARN_ON_ONCE()? I get it all
> > the time running xfstests as well.
>
> Dave insisted on it to decourage users/applications from mixing
> mmap and direct I/O.
>
> In many ways a tracepoint might be the better way to diagnose these.
sysctl suppressing those two, perhaps?
next prev parent reply other threads:[~2017-09-18 15:43 UTC|newest]
Thread overview: 11+ 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
2017-09-18 15:28 ` [XFS][trinity] " Jens Axboe
2017-09-18 15:39 ` Christoph Hellwig
2017-09-18 15:43 ` Al Viro [this message]
2017-09-18 15:51 ` Jens Axboe
2017-09-18 21:53 ` [linux-next][XFS][trinity] " 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:05 ` [linux-next][XFS][trinity] " 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=20170918154328.GA32076@ZenIV.linux.org.uk \
--to=viro@zeniv$(echo .)linux.org.uk \
--cc=abdhalee@linux$(echo .)vnet.ibm.com \
--cc=axboe@kernel$(echo .)dk \
--cc=chandan@linux$(echo .)vnet.ibm.com \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-xfs@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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