From: Nick Piggin Subject: [rfc][patch 0/3] sys_sync fixes and changes Date: Mon, 10 Nov 2008 14:22:05 +0100 Message-ID: <20081110132205.GA7183@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: linux-fsdevel@vger.kernel.org, Andrew Morton Return-path: Received: from mail.suse.de ([195.135.220.2]:52060 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754200AbYKJNWH (ORCPT ); Mon, 10 Nov 2008 08:22:07 -0500 Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, Unfortunately I had hoped to have my fsync patches for comment by now, but I have run into some problems with sys_sync and this WB_SYNC_HOLD thing. But that code seems to have a problem with data integrity anyway, and fixing that seems to get things closer to working with my fsync design (without hobbling the alternative proposal), and not to mention simplifies the more common writeback and single-file fsync cases by removing WB_SYNC_HOLD. (sync mode now becomes a very simple "data integrity" or "not data integrity" flag). I have 3 patches to this end, and would be interested in hearing comments on them. Thanks, Nick