o5r/plan9port
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

9pfuse: "fix" O_LARGEFILE on x86_64 linux (sqweek)

Browse source
This commit is contained in:
Russ Cox 2008-06-19 18:56:56 -04:00
parent 55d98d64b8
commit 7dc6d2444c
1 changed files with 14 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

17
src/cmd/9pfuse/main.c
View file

@ -24,11 +24,20 @@
#endif #endif
#ifndef O_LARGEFILE #ifndef O_LARGEFILE
# if defined(__linux__)
# define O_LARGEFILE 0100000 /* Sigh */
# else
# define O_LARGEFILE 0 # define O_LARGEFILE 0
# endif #endif
/*
* Work around glibc's broken <bits/fcntl.h> which defines
* O_LARGEFILE to 0 on 64 bit architectures. But, on those same
* architectures, linux _forces_ O_LARGEFILE (which is always
* 0100000 in the kernel) at each file open. FUSE is all too
* happy to pass the flag onto us, where we'd have no idea what
* to do with it if we trusted glibc.
*/
#if defined(__linux__)
# undef O_LARGEFILE
# define O_LARGEFILE 0100000
#endif #endif
#ifndef O_CLOEXEC #ifndef O_CLOEXEC