Re: [uml-devel] mem= and large file support

["D. Bahi" <dbahi@enterasys.com>]

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

cool - so... it's in tempfile.c : 53
make_tempfile calls mkstemp -

so maybe a build option required to get the
option in with this library call? but which?

info on libc says:

      When the sources are compiled with `_FILE_OFFSET_BITS == 64' on a
      32-bit system this function is in fact `tmpfile64', i.e. the LFS
      interface transparently replaces the old interface.

so i'll try that.

and just for 'create_mem_file' completeness
the devanon case doesn't need attention with
the mmap. right?

-----

rt_sigprocmask(SIG_UNBLOCK, [ALRM VTALRM], [ALRM VTALRM IO], 8) = 0
rt_sigprocmask(SIG_BLOCK, [IO], NULL, 8) = 0
gettimeofday({1092914208, 599204}, NULL) = 0
getpid()                                = 24405
open("/tmp/vm_file-3NJodS", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
unlink("/tmp/vm_file-3NJodS")           = 0
fchmod(3, 0777)                         = 0
_llseek(3, 2147483648, [2147483648], SEEK_SET) = 0
write(3, "\0", 1)                       = -1 EFBIG (File too large)
--- SIGXFSZ (File size limit exceeded) @ 0 (0) ---
+++ killed by SIGXFSZ +++


Jeff Dike wrote:

> dbahi@enterasys.com said:
> 
>>btw: with the 26-3um and 2.6.8.1 announce Jeff mentions the new SKAS,
>>! TT, STATIC allows mem= ~2.75G upper limit but do we need O_LARGEFILE
>>somewhere? or to compile with -D_FILE_OFFSET_64_BITS 
> 
> 
> Probably.  Can you strace that and see where E2BIG is coming from?
> 
> 				Jeff
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]