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

9pfuse: allow O_APPEND in open and create (Roman Shaposhnik)

Browse source
This commit is contained in:
Russ Cox 2008-12-30 14:27:30 -08:00
parent 0ac670585c
commit e465991ea6
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -577,6 +577,13 @@ _fuseopen(FuseMsg *m, int isdir)
openmode = flags&3; openmode = flags&3;
flags &= ~3; flags &= ~3;
flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE|O_CLOEXEC); flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE|O_CLOEXEC);
/*
* Discarding O_APPEND here is not completely wrong,
* because the host kernel will rewrite the offsets
* of write system calls for us. That's the best we
* can do on Unix anyway.
*/
flags &= ~O_APPEND;
if(flags & O_TRUNC){ if(flags & O_TRUNC){
openmode |= OTRUNC; openmode |= OTRUNC;
flags &= ~O_TRUNC; flags &= ~O_TRUNC;
@ -585,7 +592,6 @@ _fuseopen(FuseMsg *m, int isdir)
* Could translate but not standard 9P: * Could translate but not standard 9P:
* O_DIRECT -> ODIRECT * O_DIRECT -> ODIRECT
* O_NONBLOCK -> ONONBLOCK * O_NONBLOCK -> ONONBLOCK
* O_APPEND -> OAPPEND
*/ */
if(flags){ if(flags){
fprint(2, "unexpected open flags %#uo", (uint)in->flags); fprint(2, "unexpected open flags %#uo", (uint)in->flags);
@ -702,6 +708,7 @@ fusecreate(FuseMsg *m)
openmode = in->flags&3; openmode = in->flags&3;
flags &= ~3; flags &= ~3;
flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE); flags &= ~(O_DIRECTORY|O_NONBLOCK|O_LARGEFILE);
flags &= ~O_APPEND; /* see comment in _fuseopen */
flags &= ~(O_CREAT|O_TRUNC); /* huh? */ flags &= ~(O_CREAT|O_TRUNC); /* huh? */
if(flags){ if(flags){
fprint(2, "bad mode %#uo\n", in->flags); fprint(2, "bad mode %#uo\n", in->flags);