On 11/01, Oleg Nesterov wrote: > > Ah, please ignore... handler_chain() is not self-serialized, so > tu->buffer needs locking/waiting too.
Still I have to admit that I strongly dislike this yet another (and imho strange) memory pool. However, I am not going to argue because I can't suggest something better right now. But. Perhaps it makes sense to at least add a couple of trivial helpers in 10/13? Something like arg_buf_get/put/init, just to simplify the potential changes. Also. I think we should not use this pool unconditionally but again, this is another improvement we can do later. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
