Summary: | app-emulation/vmware-modules-238.4-r1 and above fails to build against hardened-sources-3.0.4-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
Component: | Current packages | Assignee: | Vadim Kuznetsov (RETIRED) <vadimk> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | pageexec, powerman-asdf, vmware+disabled |
Priority: | Normal | ||
Version: | 10.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
238-gcc-4.5.3.patch the diff file between 238.4 and 238.5 make vmci-only/linux/driver.c compatible with kernel 3.0.4 make vmmon-only/linux/driver.c compatible with kernel 3.0.4 make vmnet-only/driver.c compatible with kernel 3.0.4 fix compile errors with 3.2.2-hardened-r1 |
Description
Anton Bolshakov
2011-09-28 00:18:05 UTC
Created attachment 288173 [details]
238-gcc-4.5.3.patch
I have moved the initialisation of the "file_operations" structure to the static initialiser. It compiles fine now, however I don't have a test machine and can not verify if it's really working.
FYI, the vmware overlay has app-emulation/vmware-modules-238.5 where the problem is fixed. Created attachment 290023 [details]
the diff file between 238.4 and 238.5
ok, my patch is wrong, don't use it. Sadly, version 4.0 has the same problem, so I have created a diff file between 238.4 and 238.5. It should give a clue how to fix it in the latest version.
Sorry, it could be the compatibility problem with kernel 3.0.1 instead, similar with the bug #386721. My first patch looks the same too. *** Bug 390077 has been marked as a duplicate of this bug. *** I've created patches for vmware-modules-264.1, similar to patch used for open-vm-tools-kmod in bug 386721. With these 3 patches I've successfully build vmware-modules-264.1 and run vmware-workstation-8.0.1.528992-r1 with kernel 3.0.4-hardened-r5. Probably these 3 patches should be joined in one. Created attachment 295017 [details, diff]
make vmci-only/linux/driver.c compatible with kernel 3.0.4
Created attachment 295019 [details, diff]
make vmmon-only/linux/driver.c compatible with kernel 3.0.4
Created attachment 295021 [details, diff]
make vmnet-only/driver.c compatible with kernel 3.0.4
Created attachment 301473 [details, diff] fix compile errors with 3.2.2-hardened-r1 I've found this patch on http://weltall.heliohost.org/wordpress/2012/01/26/vmware-workstation-8-0-2-player-4-0-2-fix-for-linux-kernel-3-2-and-3-3/ and it fixes compile issue with 3.2 kernels. I've added patched ebuild for app-emulation/vmware-modules-264.1 to my overlay 'powerman' - until these patches will be added to 'vmware' overlay or main portage. I'm closing this bug because the problem is solved in the latest 264.4 version. vmware@gentoo: your idleness worked out just fine. The same bug hits me with x86_64 3.4.2-hardened-r1 kernel and vmware-modules-264.4. MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.4.2-hardened-r1' CC [M] /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/vmciKernelIf.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/common/vmciDriver.o CC [M] /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/common/vmciResource.o /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c: In function 'vmci_host_init': /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:387:4: warning: passing argument 1 of 'memset' discards qualifiers from pointer target type /usr/src/linux-3.4.2-hardened-r1/arch/x86/include/asm/string_64.h:55:7: note: expected 'void *' but argument is of type 'const struct file_operations *' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:388:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:389:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:391:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:396:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:398:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:399:4: error: assignment of read-only variable 'vmuser_fops' /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c: In function '__check_disable_host': /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c: In function '__check_disable_guest': /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c: In function '__check_disable_msi': /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c: In function '__check_disable_msix': /var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only/linux/driver.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only] Error 2 make[1]: *** [sub-make] Error 2 make[1]: Leaving directory `/usr/src/linux-3.4.2-hardened-r1' make: *** [vmci.ko] Error 2 * ERROR: app-emulation/vmware-modules-264.4 failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-264.4'`, * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-264.4'`. * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-264.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-264.4/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-264.4/work/vmci-only' * S: '/var/tmp/portage/app-emulation/vmware-modules-264.4/work' (In reply to comment #13) > The same bug hits me with x86_64 3.4.2-hardened-r1 kernel and > vmware-modules-264.4. with USE=pax_kernel? don't using pax in kernel and use flag pax-kernel was set off with USE="pax-kernel" it works. now i can crash my machine with starting a vm. (In reply to comment #16) > now i can crash my machine with starting a vm. That is the dead end, a long term and very annoying bug #382793 |