User: Password:
|
|
Subscribe / Log in / New account

Re: [RFC][BZ #14627] Make linux close errno to EINPROGRESS when interrupted in signal.

From:  David Miller <davem-AT-davemloft.net>
To:  dalias-AT-aerifal.cx
Subject:  Re: [RFC][BZ #14627] Make linux close errno to EINPROGRESS when interrupted in signal.
Date:  Thu, 05 Dec 2013 15:50:09 -0500 (EST)
Message-ID:  <20131205.155009.707968344039994800.davem@davemloft.net>
Cc:  hch-AT-lst.de, azanella-AT-linux.vnet.ibm.com, libc-alpha-AT-sourceware.org
Archive-link:  Article

From: Rich Felker <dalias@aerifal.cx>
Date: Thu, 5 Dec 2013 15:11:26 -0500

> If EINTR from close essentially doesn't show up in the wild on Linux,
> I think the proposed change in glibc to replace it with EINPROGRESS
> would essentially be just a safety against (dangerous!) double-close
> bugs in correct POSIX applications due to strange devices slipping an
> EINTR through. I'm still strongly in favor of adding it (or a
> replacement with 0/success).

At one time many years ago there was a path in the kernel that
returned an error from close and it broke so many things.  Even emacs
crashed.

The widespread overwhelming belief is that close() is just going
to always succeed, and there is more harm than good from signalling
errors at all from that function.



(Log in to post comments)


Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds