Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758674Ab3GPD3S (ORCPT ); Mon, 15 Jul 2013 23:29:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20365 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753834Ab3GPD3R (ORCPT ); Mon, 15 Jul 2013 23:29:17 -0400 Date: Mon, 15 Jul 2013 23:28:41 -0400 From: Dave Jones To: Linus Torvalds Cc: Linux Kernel , Peter Zijlstra , Alexander Viro , Oleg Nesterov , Ben Myers , xfs@oss.sgi.com Subject: Re: splice vs execve lockdep trace. Message-ID: <20130716032841.GB1578@redhat.com> Mail-Followup-To: Dave Jones , Linus Torvalds , Linux Kernel , Peter Zijlstra , Alexander Viro , Oleg Nesterov , Ben Myers , xfs@oss.sgi.com References: <20130716015305.GB30569@redhat.com> <20130716023847.GA31481@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 745 Lines: 20 On Mon, Jul 15, 2013 at 08:25:14PM -0700, Linus Torvalds wrote: > And looking more at that, I'm actually starting to think this is an > XFS locking problem. XFS really should not call back to splice while > holding the inode lock. > > But that XFS code doesn't seem new either. Is XFS a new thing for you > to test with? I started pounding on it fairly recently and have shook out a number of bugs (now fixed) since I started, so relatively new, but on the order of 'months' now. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/