Re: [PATCH] making dump EINTR resistant

On  6 Jun, Bruce Evans wrote:

>> Stevens lists only ioctl, read, readv, write, writev, wait and waitpid,
>> but not open, fopen, close and fclose. What about those?
> 
> Stevens is correct, but in practice open() and close() often ignores signals
> while it is in the kernel, so signal delivery occurs when the process is
> about to leave the kernel and doesn't result in the syscall returning
> EINTR.  I think this (no EINTR) happens for regular files and disk devices.
> It doesn't happen for slow devices like terminals, and shouldn't happen if
> the syscall can block (then the device driver must support the syscall
> being aborted by a signal).

So why produced dump a EINTR error for me on 4.x and for Benjamin on
-current?

Bye,
Alexander.

-- 
   "One world, one web, one program"  -- Microsoft promotional ad
         "Ein Volk, ein Reich, ein Fuehrer"  -- Adolf Hitler

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-audit" in the body of the message