I've patched the rcuread*lock() issue and the modules load and I can run guests OK, but trying to use vmware-netcfg hangs.
I did an "strace" and it appears the issue is it's expecting an answer from a pipe that never comes (I didn't do much more tracing than that).
Considering there's been some RCU/locking changes in the networking code between 6.8 and 6.9 I suspect I could bisect the actual change in the kernel, but I figured I should at least report it here as well. I looked at the module code to see if there could be a deadlock there after the RCU lock changes, but nothing immediately stood out (i.e., all the rcu_read_lock()ed points seemed to have matching _unlock() points as required).
What worries me is I hope the issue isn't in one of VMWare's proprietary binaries :|
I've patched the rcuread*lock() issue and the modules load and I can run guests OK, but trying to use vmware-netcfg hangs.
I did an "strace" and it appears the issue is it's expecting an answer from a pipe that never comes (I didn't do much more tracing than that).
Considering there's been some RCU/locking changes in the networking code between 6.8 and 6.9 I suspect I could bisect the actual change in the kernel, but I figured I should at least report it here as well. I looked at the module code to see if there could be a deadlock there after the RCU lock changes, but nothing immediately stood out (i.e., all the rcu_read_lock()ed points seemed to have matching _unlock() points as required).
What worries me is I hope the issue isn't in one of VMWare's proprietary binaries :|