From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: file offset corruption on 32-bit machines? Date: Thu, 10 Apr 2008 17:33:47 +0200 Message-ID: <87k5j5n2qs.fsf@basil.nowhere.org> References: <200804101555.58643.mhocko@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Meelis Roos , Linux Kernel list , linux-fsdevel@vger.kernel.org To: Michal Hocko Return-path: Received: from smtp-out01.alice-dsl.net ([88.44.60.11]:5533 "EHLO smtp-out01.alice-dsl.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756721AbYDJPf4 (ORCPT ); Thu, 10 Apr 2008 11:35:56 -0400 In-Reply-To: <200804101555.58643.mhocko@suse.cz> (Michal Hocko's message of "Thu, 10 Apr 2008 15:55:58 +0200") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Michal Hocko writes: > [Adding fsdevel list] > > On Tuesday 08 April 2008 10:05:47 am Meelis Roos wrote: >> Jeff Robertson analyzes the behaviour of different operating systems' >> 64-bit file offset implementation and concludes that on 32-bit >> machines, Linux and Solaris lack any locking to keep the two 32-bit >> halves in sync and this could cause rare file offset corruption. >> >> http://jeffr-tech.livejournal.com/21014.html > > AFAICS, this race is theoretically possible, but it is very hard (almost > impossible) to trigger with a sane file usage pattern. We discussed this extensively some time ago in http://thread.gmane.org/gmane.linux.file-systems/20712/focus=20771 No solution so far -Andi