12210fe578
This fixes a busy loop by working around a quirk with Linux kernels
<= 2.6.32 where an EPIPE or ECONNRESET error on a file descriptor that
is polled for EPOLLOUT but not EPOLLIN gets reported by epoll_wait() as
just EPOLLERR|EPOLLHUP, like this:
epoll_wait(5, {{EPOLLERR|EPOLLHUP, {u32=12, u64=12}}}, 1024, 433) = 1
Before this commit, libuv called uv__read() which attempts to read from
the file descriptor. With newer kernels and on other operating systems
that fails like this:
read(12, "", 65536) = -1 EPIPE (Broken pipe)
Which tells libuv there is a connection error and it should notify the
user of that. On the affected Linux kernels however, the read succeeds
with an EOF:
read(12, "", 65536) = 0
Which is subsequently passed on to the user. In most cases, the user
will close the handle and everything is fine.
Node.js however sometimes keeps the handle open in an attempt to flush
pending write requests. While libuv doesn't officially support this,
unofficially it works...
...except on those older kernels. Because the kernel keeps waking up
the event loop without setting POLLOUT and because the read calls EOF
but don't error, libuv's I/O state machine doesn't progress.
That's why this commit changes uv__stream_io() to also write pending
data. While the read() system call doesn't error, the write() system
call will.
Fixes joyent/node#5504.
|
||
|---|---|---|
| include | ||
| src | ||
| test | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| build.mk | ||
| ChangeLog | ||
| checksparse.sh | ||
| common.gypi | ||
| config-mingw.mk | ||
| config-unix.mk | ||
| gyp_uv | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| uv.gyp | ||
| vcbuild.bat | ||
libuv
libuv is a new platform layer for Node. Its purpose is to abstract IOCP on Windows and epoll/kqueue/event ports/etc. on Unix systems. We intend to eventually contain all platform differences in this library.
Features
-
Non-blocking TCP sockets
-
Non-blocking named pipes
-
UDP
-
Timers
-
Child process spawning
-
Asynchronous DNS via
uv_getaddrinfo. -
Asynchronous file system APIs
uv_fs_* -
High resolution time
uv_hrtime -
Current executable path look up
uv_exepath -
Thread pool scheduling
uv_queue_work -
ANSI escape code controlled TTY
uv_tty_t -
File system events Currently supports inotify,
ReadDirectoryChangesWand kqueue. Event ports in the near future.uv_fs_event_t -
IPC and socket sharing between processes
uv_write2
Community
Documentation
- include/uv.h — API documentation in the form of detailed header comments.
- An Introduction to libuv — An overview of libuv with tutorials.
- LXJS 2012 talk - High-level introductory talk about libuv.
- Tests and benchmarks - API specification and usage examples.
Build Instructions
For GCC (including MinGW) there are two methods building: via normal makefiles or via GYP. GYP is a meta-build system which can generate MSVS, Makefile, and XCode backends. It is best used for integration into other projects. The old system is using plain GNU Makefiles.
To build via Makefile simply execute:
make
MinGW users should run this instead:
make PLATFORM=mingw
Out-of-tree builds are supported:
make builddir_name=/path/to/builddir
To build with Visual Studio run the vcbuild.bat file which will checkout the GYP code into build/gyp and generate the uv.sln and related files.
Windows users can also build from cmd-line using msbuild. This is done by running vcbuild.bat from Visual Studio command prompt.
To have GYP generate build script for another system, make sure that you have Python 2.6 or 2.7 installed, then checkout GYP into the project tree manually:
mkdir -p build
svn co http://gyp.googlecode.com/svn/trunk build/gyp
Or:
mkdir -p build
git clone https://git.chromium.org/external/gyp.git build/gyp
Unix users run
./gyp_uv -f make
make -C out
Macintosh users run
./gyp_uv -f xcode
xcodebuild -project uv.xcodeproj -configuration Release -target All
Note for UNIX users: compile your project with -D_LARGEFILE_SOURCE and
-D_FILE_OFFSET_BITS=64. GYP builds take care of that automatically.
Note for Linux users: compile your project with -D_GNU_SOURCE when you
include uv.h. GYP builds take care of that automatically. If you use
autotools, add a AC_GNU_SOURCE declaration to your configure.ac.
Supported Platforms
Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW.
Linux 2.6 using the GCC toolchain.
MacOS using the GCC or XCode toolchain.
Solaris 121 and later using GCC toolchain.