Closed munix9 closed 1 year ago
This is surprising, I have 17.0.1 on a 6.3-rc1 kernel (and 6.2 before that) and never hit the field spanning check. Does this happen right after loading the module (as it used to with unpatched 17.0.0) or do you need to do something specific to trigger it?
As far as I can see, it only shows up when a VM is started, not when the module itself is loaded.
I'm still checking to see if it only occurs under certain VM's, would be odd but nothing is impossible. But this may take some time.
I can see it now... Sadly, VMware developers used the union wrapper to get rid of the more obvious warning in VNetEvent_Send()
but they ignored that exactly the same problem exists also in VNetUserListenerEventHandler()
except it only shows on a VM start rather than on module load.
Current workstation-17.0.1
head (commit 650fb3abeb82) should fix that, can you give it a try?
Ah, ok, wonderful and thanks for the possible solution. I will try it out and report back, but it may take some time.
It looks good, thanks for the solution.
Thank you for the feedback. (And for an actual issue report, unfortunately those are quite rare here.)
The problem has already been discussed here. It was fixed with the patch https://github.com/mkubecek/vmware-host-modules/commit/78b77816d39a77b1643426ece1ebd48776d83c1b for workstation-17.0.0, but occurs again in workstation-17.0.1 because the patch is missing there.
The patch is probably also not easy to apply, because among other things the definition
VNet_EventHeader event;
has been changed in workstation-17.0.1 toopenSUSE Tumbleweed 20230310 Kernel 6.2.2-1-default vmware-host-modules branch workstation-17.0.1 VMware-Workstation-Full-17.0.1-21139696