This could be an indication that epoll of an epoll fd should not be
allowed. This kind of sucks as epoll event hierarchies appear, at
least on the surface, very natural, and better than poll()/epoll.
Another option would be to allow a reasonable depth (2? 3?). The extra
checking (depth calculation) only needs to be performed if a file is
added or removed where f_op == epoll_f_op.
mark
-- mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder |\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | | | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, CanadaOne ring to rule them all, one ring to find them, one ring to bring them all and in the darkness bind them...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/