[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170910025712.GC5426@ZenIV.linux.org.uk>
Date: Sun, 10 Sep 2017 03:57:21 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Dave Jones <davej@...emonkey.org.uk>,
Dave Chinner <david@...morbit.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-xfs@...r.kernel.org
Subject: Re: iov_iter_pipe warning.
On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote:
> With this in place, I'm still seeing -EBUSY from invalidate_inode_pages2_range
> which doesn't end well...
Different issue, and I'm not sure why that WARN_ON() is there in the
first place. Note that in a similar situation generic_file_direct_write()
simply buggers off and lets the caller do buffered write...
iov_iter_pipe() warning is a sign of ->read_iter() on pipe-backed iov_iter
putting into the pipe more than it claims to have done.
Powered by blists - more mailing lists