Re: xfs_file_splice_read: possible circular locking dependency detected

CAI Qian <[email protected]>
Newsgroups gmane.comp.file-systems.xfs.general
Message-ID <[email protected]>

----- Original Message -----
> From: "Linus Torvalds" <[email protected]>
> To: "CAI Qian" <[email protected]>
> Cc: "Dave Chinner" <[email protected]>, "Al Viro" <[email protected]>, "linux-xfs"
> <[email protected]>, [email protected]
> Sent: Thursday, September 8, 2016 2:01:23 PM
> Subject: Re: xfs_file_splice_read: possible circular locking dependency detected
> 
> On Thu, Sep 8, 2016 at 8:29 AM, CAI Qian <[email protected]> wrote:
> > Right. FYI, revert the commit below fixes the regression,
> >
> > 8d02076 : ->splice_write() via ->write_iter()
> 
> I guess you didn't actually revert that, because so much else has
> changed. So you just tested the pre- and post- state of that commit?
Right, I just reverted that commit while that one is as a HEAD. It is
not going to be a straight-forward revert. There have had a few commits
on the top already, so there will be some additional work to bake a proper
revert to the current origin HEAD.

Though, Everything else looks straigtforward (PAGE_CACHE_* conversion,
inode_lock* conversion, file_remove_privs() converstion). It seems only
tricky thing is that generic_write_sync() starts to use struct kiocb *
instead of struct file *, so generic_file_splice_write() and probably
xfs_file_splice_write() need to change to use kiocb as well.
   CAI Qian

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.