Date: Sat, 10 Aug 2002 15:04:35 +0100 From: Ian Dowse <iedowse@maths.tcd.ie> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: bhlewis@wossname.net, freebsd-current@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <200208101504.aa40149@salmon.maths.tcd.ie> In-Reply-To: Your message of "Sat, 10 Aug 2002 15:23:54 %2B0200." <20020810152354.470317e4.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020810152354.470317e4.Alexander@Leidinger.net>, Alexander Leiding er writes: >Have a look at Message-ID: <20020606063157.V8685-100000@gamplex.bde.org> >(should be in the archive of audit). Ah, I had forgotten about that -audit thread. >Short: open shouldn't be able to return EINTR in practice... > >My assumptions: > - Bruce hasn't made a mistake > - something broke in the kernel (either for a "short" period of > time, or it's still broken), so we should look for the real > problem instead I had a quick look yesterday, and I found a PCATCH tsleep call in diskopen(), though I do not know if this is the one that affects dump. Does open(2) need to loop on ERESTART? Currently it just maps ERESTART to EINTR and returns the error. We should fix this broken dump behaviour anyway - I don't think it matters too much for now whether it is fixed in userland or the kernel, as it will only affect the tiny set of applications that receive signals while opening a disk device at the same time as another open on the same device is occurring (I think). Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200208101504.aa40149>