tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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

To: Emmanuel Dreyfus <manu%netbsd.org@localhost>
Subject: Re: [PATCH] PUFFS backend allocation (round 3)
From: Taylor R Campbell <campbell+netbsd-tech-kern%mumble.net@localhost>
Date: Wed, 29 Oct 2014 15:33:43 +0000

   Date: Wed, 29 Oct 2014 00:11:41 +0000
   From: Emmanuel Dreyfus <manu%netbsd.org@localhost>

   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
   close again, what should happen? Success? 

Nope.  close(2) guarantees the file descriptor is closed, even if it
returns an error.

References:
- Re: [PATCH] PUFFS backend allocation (round 3)
  - From: Emmanuel Dreyfus

Prev by Date: Re: [PATCH] PUFFS backend allocation (round 3)
Next by Date: Re: [PATCH] PUFFS backend allocation (round 3)
Previous by Thread: Re: [PATCH] PUFFS backend allocation (round 3)
Next by Thread: netbsd32_compat_50 inconsistency
Indexes:

Home | Main Index | Thread Index | Old Index