Summary: | app-emulation/vmware-modules-271.2 with >=sys-kernel/hardened-sources-3.8.2-r1 - vsock-only/linux/af_vsock.c:3163:7: error: assignment of member ‘family’ in read-only object | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | iGentoo <AlphatPC> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Kernel Team (OBSOLETE) <hardened-kernel+disabled> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | hlein, hydrapolic, pageexec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
vmware-modules-271.2-build.log
vsock-constify.patch vsock-pax-const.patch openvm_hardened399_build.log |
Description
iGentoo
2013-03-15 23:33:10 UTC
something like this should work: http://pastebin.com/dVPszctW (In reply to PaX Team from comment #1) > something like this should work: http://pastebin.com/dVPszctW PaX Team, your link has expired, could you repost it?.. Created attachment 349764 [details, diff]
vsock-constify.patch
Created attachment 349766 [details, diff]
vsock-pax-const.patch
What is the state of this bug? Still a problem. Anything for us to do here? (In reply to Anthony Basile from comment #5) > What is the state of this bug? Still a problem. Anything for us to do here? if i'm not mistaken, vsock is in 3.9 now and should compile fine. I'm still getting this issue when pax options are enabled in the kernel: /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.c: In function ‘VSockVmciRegisterAddressFamily’: /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.c:3163:7: error: assignment of member ‘family’ in re ad-only object /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.c:3167:10: error: assignment of member ‘family’ in r ead-only object /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.c: In function ‘VSockVmciUnregisterAddressFamily’: /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.c:3205:4: error: assignment of member ‘family’ in re ad-only object make[3]: *** [/var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/af_vsock.o] Error 1 make[2]: *** [_module_/var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only] Error 2 make[1]: *** [sub-make] Error 2 make[1]: Leaving directory `/usr/src/linux-3.9.7-hardened' make: *** [vsock.ko] Error 2 * ERROR: app-emulation/vmware-modules-271.2 failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=app-emulation/vmware-modules-271.2'`, * the complete build log and the output of `emerge -pqv '=app-emulation/vmware-modules-271.2'`. * The complete build log is located at '/var/tmp/portage/app-emulation/vmware-modules-271.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-emulation/vmware-modules-271.2/temp/environment'. * Working directory: '/var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only' * S: '/var/tmp/portage/app-emulation/vmware-modules-271.2/work' # uname -a Linux akarin 3.9.7-hardened #1 SMP Wed Jun 26 06:36:36 PDT 2013 x86_64 Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz GenuineIntel GNU/Linux (In reply to Mike from comment #7) > I'm still getting this issue when pax options are enabled in the kernel: > > /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/ > af_vsock.c: In function ‘VSockVmciRegisterAddressFamily’: i guess vsock should be disabled in vmware-modules when compiling for linux 3.9 since it has its own vsock module now. (In reply to PaX Team from comment #8) > (In reply to Mike from comment #7) > > I'm still getting this issue when pax options are enabled in the kernel: > > > > /var/tmp/portage/app-emulation/vmware-modules-271.2/work/vsock-only/linux/ > > af_vsock.c: In function ‘VSockVmciRegisterAddressFamily’: > > i guess vsock should be disabled in vmware-modules when compiling for linux > 3.9 since it has its own vsock module now. Yeah, I remember reading that VSOCK was going to be included in the kernel. Either way, I'll have to leave the fix up to the teams working on the bug. I just wanted to submit a report saying I'm still having the issue with the 3.9 kernel. Same for app-emulation/open-vm-tools-kmod-2013.04.16.1098359 with hardened-sources-3.9.9. Created attachment 354606 [details]
openvm_hardened399_build.log
This is an old bug which I was never really able to test. Is the readonly object fixed? This got fixed in latest open-vm-tools-kmod where the building of vsock is disabled on kernel > 3.9 since it's already upstream. |