Date: Thu, 6 Jun 2002 12:37:57 +0200 (CEST) From: Alexander Leidinger <Alexander@Leidinger.net> To: bde@zeta.org.au Cc: netchild@FreeBSD.ORG, audit@FreeBSD.ORG, bhlewis@wossname.net Subject: Re: [PATCH] making dump EINTR resistant Message-ID: <200206061038.g56AbviS000861@Magelan.Leidinger.net> In-Reply-To: <20020606063157.V8685-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org
with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206061038.g56AbviS000861>