Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756403Ab3GQQDO (ORCPT ); Wed, 17 Jul 2013 12:03:14 -0400 Received: from mail-ve0-f170.google.com ([209.85.128.170]:40852 "EHLO mail-ve0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754175Ab3GQQDM (ORCPT ); Wed, 17 Jul 2013 12:03:12 -0400 MIME-Version: 1.0 In-Reply-To: <20130717055103.GK11674@dastard> References: <20130716023847.GA31481@redhat.com> <20130716060351.GE11674@dastard> <20130716193332.GB3572@sgi.com> <20130716204335.GH11674@dastard> <20130717040616.GI11674@dastard> <20130717055103.GK11674@dastard> Date: Wed, 17 Jul 2013 09:03:11 -0700 X-Google-Sender-Auth: yjBo46645n3Fe982vp94N1q1G-M Message-ID: Subject: Re: splice vs execve lockdep trace. From: Linus Torvalds To: Dave Chinner Cc: Ben Myers , Peter Zijlstra , Oleg Nesterov , Linux Kernel , Alexander Viro , Dave Jones , xfs@oss.sgi.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 20 On Tue, Jul 16, 2013 at 10:51 PM, Dave Chinner wrote: > > But When i say "stale data" I mean that the data being returned > might not have originally belonged to the underlying file you are > reading. We're still talking at cross purposes then. How the hell do you handle mmap() and page faulting? Because if you return *that* kind of stale data, than you're horribly horribly buggy. And you cannot *possibly* blame generic_file_splice_read() on that. Linus -- 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/