> > Well, no, that'd only work with an open connection :) Actually, it also works fairly easily for when firmware has 4-way- handshake offload, which will be coming to a kernel near you soon. > And even that is questionable in my mind for some of the more > advanced cases. Well, at least in that case you can have things running (for a while) if the manager crashes? > But I'm not sure what your point is, do you still have objections to > this approach? Well, first of all, you can keep things running, at least until you've figured out how to restart wpa_supplicant/whatever. There also aren't really any important resources to clear when userspace dies, at least nothing that userspace can't trivially clear later by disconnecting (even unconditionally and ignoring the result)... So basically I just don't see the advantage. It feels like trading a single line of userspace code to disconnect with some (not super complex, but still somewhat involved) kernel-side tracking. That doesn't really seem like a worthwhile tradeoff to me. johannes
