Re: [PATCH] PUFFS backend allocation (round 3)

[manu%netbsd.org@localhost (Emmanuel Dreyfus)]

Thor Lancelot Simon <tls%panix.com@localhost> wrote:

> > Let me rephrase: I call close(), get a error because of a failed
> > asynchronous write. The file is not closed, right? Now if I call
> 
> Wrong.  It's still closed.

Thank you for that helpful explanation.

Another concern: a file may be open by multiple processes. If close()
raise any write error done on the vnode, how can I avoid sending the
error to a process that did not issue the write operation?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost