| To: | CAI Qian <caiqian@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_file_splice_read: possible circular locking dependency detected |
| From: | Al Viro <viro@xxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 8 Sep 2016 18:56:32 +0100 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, linux-xfs <linux-xfs@xxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1450936953.949798.1473348551588.JavaMail.zimbra@xxxxxxxxxx> |
| References: | <723420070.1340881.1472835555274.JavaMail.zimbra@xxxxxxxxxx> <1832555471.1341372.1472835736236.JavaMail.zimbra@xxxxxxxxxx> <20160903003919.GI30056@dastard> <1450936953.949798.1473348551588.JavaMail.zimbra@xxxxxxxxxx> |
| Sender: | Al Viro <viro@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.6.1 (2016-04-27) |
On Thu, Sep 08, 2016 at 11:29:11AM -0400, CAI Qian wrote: > > Nope, this goes back to the splice rework back around ~3.16, IIRC. > Right. FYI, revert the commit below fixes the regression, > > 8d02076 : ->splice_write() via ->write_iter() ... and brings back a lot of other crap. The thing is, pipe lock should be on the outside of everything fs might be taking, so that splice IO is the same as normal IO as far as filesystem locking is concerned. For the write side it had been done in that commit, for the read side it's yet to be done. |
| Previous by Date: | Re: [PATCH 06/71] xfs: set up per-AG free space reservations, Darrick J. Wong |
|---|---|
| Next by Date: | Re: xfs_file_splice_read: possible circular locking dependency detected, Linus Torvalds |
| Previous by Thread: | Re: xfs_file_splice_read: possible circular locking dependency detected, CAI Qian |
| Next by Thread: | Re: xfs_file_splice_read: possible circular locking dependency detected, Linus Torvalds |
| Indexes: | [Date] [Thread] [Top] [All Lists] |