On Tue, 2008-03-25 at 12:23 +1100, Robert Collins wrote: > Is it valgrind being wrong, or does epoll actually read from that > unitinitialised region?
it's valgrind not knowing (or caring about) the full details of when epoll uses what of the supplied data. But generally speaking it's a good warning as supplying uninitialized input data to the kernel even if that data is currently unused for the specific call details is perhaps not a good idea. Regards Henrik