On Wed, Apr 15, 2009 at 07:56:42AM -0700, Eric W. Biederman wrote: > > I still have the feeling that putting the socket in tun_file instead > of in tun_struct might be conceptually cleaner, but one big blob that > is allocated and destroyed together is certainly easier and a lot > less racy to deal with. As I said the difficulty with putting the socket in tun_file is how do you get it on the RX callback path without introducing new races. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
