Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932225Ab1CNB7E (ORCPT ); Sun, 13 Mar 2011 21:59:04 -0400 Received: from smarthost1.greenhost.nl ([195.190.28.78]:46176 "EHLO smarthost1.greenhost.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755818Ab1CNB7C (ORCPT ); Sun, 13 Mar 2011 21:59:02 -0400 Message-ID: <10d164106e8d30b89d7263b067db01f0.squirrel@webmail.greenhost.nl> In-Reply-To: <4D7D7325.2040708@garzik.org> References: <201103111255.44979.arnd@arndb.de> <4D7AC0FE.8070806@gmail.com> <1d4d1b7ae64da97f44cad0e2bda4f832.squirrel@webmail.greenhost.nl> <4D7ADFDD.9080108@gmail.com> <4D7BBC03.3020404@garzik.org> <89481603ed9cfc86efaa039c2dfeb955.squirrel@webmail.greenhost.nl> <4D7D7325.2040708@garzik.org> Date: Mon, 14 Mar 2011 02:59:00 +0100 (CET) Subject: Re: [PATCH v3] introduce sys_syncfs to sync a single file system From: "Indan Zupancic" To: "Jeff Garzik" Cc: "Ric Wheeler" , "Arnd Bergmann" , "Sage Weil" , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, "Aneesh Kumar K. V" , "Jonathan Nieder" , akpm@linux-foundation.org, linux-api@vger.kernel.org, mtk.manpages@gmail.com, viro@zeniv.linux.org.uk, hch@lst.de, l@jasper.es User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -0.6 X-Scan-Signature: 7194f67edb0fd0030ea28d62f3968513 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 735 Lines: 17 On Mon, March 14, 2011 02:45, Jeff Garzik wrote: > On 03/13/2011 09:31 PM, Indan Zupancic wrote: >> The new syscall works on only one fd too. The behaviour of the proposed >> syncfs and an extended sync_file_range is exactly the same. > > No, it's not. You should read the patch before commenting. Have you read my sync_file_range patch? Because it's exactly the same code, but put in sync_file_range instead of a new system call. How that can have different behaviour, I have no idea. -- 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/