From: Marcelo Ricardo Leitner <marcelo.leitner@xxxxxxxxx> Date: Wed, 9 Sep 2015 17:03:01 -0300 > So the fix then is to invert the initialization order inside > register_pernet_subsys() so that the control socket is created by last > and also block socket creation if netns initialization wasn't yet > performed. If we really need to we could make ->create() fail with -EAFNOSUPPORT if kern==1 until the protocol is fully setup. Or, instead of failing, we could make such ->create() calls block until the control sock init is complete or fails. We have actually several visibility issues wrt. control sockets on protocol init, in general. For example, such control sockets can briefly be hashed and visible to socket dumps and packet input. A lot of really tricky issues involved here. -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
