Okay!
I've spun nightlies now and will be running IKE-STC on 'em soon, but here is
an improved webrev with a new bug:
http://cr.opensolaris.org/~danmcd/6777776/
and the new bug is:
6779183 AH and ESP taskq handlers have to remember the netstack ID.
For now, I stuck with the existing *_kcf_callback() strategy of tagging the
packet with the netstack ID, followed by a followup check and refhold. I
didn't perform a refhold prior to the asynchrony because I figured the
original IP Instance putback didn't do a refhold across the asynchrony of
crypto for a reason.
I know there's serious rewhacking of the IP datapath occurring, so it's
possible some of these sources of double-locking that 6777776 exposes will
disappear, but I'd like folks to take a look at the here-and-now fix.
Thanks!
Dan
_______________________________________________
networking-discuss mailing list
[email protected]
