Cyril Hrubis <chrubis@xxxxxxx> writes: > Hi! >> > The io_* manuals says that we should use aio_context_t as type for aio >> > handle. That is wrong as the functions are defined with io_context_t >> > (libaio.h). Patch attached. >> > >> > The only oustanding issue is that manual for io_setup says that we must >> > set the io_context_t to 0 before use. And as the io_context_t is defined >> > as opaque type (and it's defined as pointer now) the only way to >> > initalize it without warnigs is memset(&ctxp, 0, sizeof(ctxp));. Perhaps >> > this is not needed at all, as the ctpx is passed to the syscall and then >> > initalized in the kernel (at least I haven't seem any checks in the >> > codepath). >> >> There are checks in place for this, so the man page should not change in >> that regard. > > So should we settle for memset()? I could update send updated patch > then. Yeah, memset is what I typically have done. Thanks, Cyril. -Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
