[lkml]   [1998]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2G file size limitation question
> 	And yet, the code check that it can't write beyond 2^32 bits,
> because then it can't write the size into the i-node.
> Also the i-node kept in RAM holds i_size as __u32, and
> many things trust that, and some write there SIGNED 32-bit
> values -- I think the ftruncate() is one. (Sigh..)

You need ftruncate64() on intel and 64bit ftruncate otherwise. I spent
half of today looking at 64bit issues for a contract and the more you look
the worse it gets (locking isnt 64bit clean)

> IMO, the VMM/VFS layer need to become pure 64-bit, before
> we can benefit from having fully 64-bit backends.

mmap64() is needed for 64bit offset <32bit sized maps on all platforms


 \ /
  Last update: 2005-03-22 13:41    [W:0.090 / U:3.280 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site