From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [patch 5/6] splice: remove generic_file_splice_write_nolock() Date: Tue, 14 Apr 2009 19:22:42 +0100 Message-ID: <20090414182242.GG32311@shareable.org> References: <20090414174835.487031939@szeredi.hu> <20090414174859.496563416@szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: jens.axboe@oracle.com, mfasheh@suse.com, akpm@linux-foundation.org, viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Miklos Szeredi Return-path: Received: from mail2.shareable.org ([80.68.89.115]:57311 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752966AbZDNSW6 (ORCPT ); Tue, 14 Apr 2009 14:22:58 -0400 Content-Disposition: inline In-Reply-To: <20090414174859.496563416@szeredi.hu> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Miklos Szeredi wrote: > Remove the now unused generic_file_splice_write_nolock() function. > It's conceptually broken anyway, because splice may need to wait for > pipe events so holding locks across the whole operation is wrong. Did the conceptual brokenness affect userspace behaviour of splice/sendfile at all? Thanks, -- Jamie