[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200810081949.00556.nickpiggin@yahoo.com.au>
Date: Wed, 8 Oct 2008 19:48:59 +1100
From: Nick Piggin <nickpiggin@...oo.com.au>
To: Eric Dumazet <dada1@...mosbay.com>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Hisashi Hifumi <hifumi.hisashi@....ntt.co.jp>,
torvalds@...ux-foundation.org,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
"Theodore Ts'o" <tytso@....edu>
Subject: Re: [RESEND] [PATCH] VFS: make file->f_pos access atomic on 32bit arch
On Wednesday 08 October 2008 19:32, Eric Dumazet wrote:
> A far more interesting problem is the "tail -f logfile" problem that raised
> recently in lkml, when file is NFS mounted, where reader can get nul
> bytes... (Subject : blocks of zeros (NULLs) in NFS files in kernels >=
> 2.6.20 )
Not so interesting outside NFS, AFAIKS? It's just a matter of what
semantics NFS chooses to implement... I guess stronger semantics
will tend to be more costly, all else being equal, probably the
reason why they do it that way.
That behaviour does seem a bit surprising, though.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists