Hello. Vadim Korschok wrote: > Still not working after disable TOMOYO Linux, dmesg output: Hmm...
> Call Trace: > [<ffffffffa0016b9b>] ? kvm_arch_vcpu_put+0xe/0x218 [kvm] > [<ffffffffa001313d>] ? vcpu_put+0x9/0x9d [kvm] > [<ffffffffa00196d1>] ? kvm_arch_vcpu_ioctl_run+0x5df/0x5ea [kvm] > [<ffffffffa001474b>] ? kvm_resched+0x1c5/0x1048 [kvm] > [<ffffffff802444e1>] ? do_futex+0xb0/0x79f > [<ffffffff80265533>] ? handle_mm_fault+0x387/0x6fb > [<ffffffff8034a843>] ? ccs_capable+0x33/0x1a6 > [<ffffffff8028a2a6>] ? vfs_ioctl+0x46/0x8f > [<ffffffff8028a518>] ? do_vfs_ioctl+0x229/0x235 > [<ffffffff8028a575>] ? sys_ioctl+0x51/0x74 > [<ffffffff8020250b>] ? system_call_fastpath+0x16/0x1b You got a different trace, but ccs_capable() from vfs_ioctl() remains. Though '?' indicates that that line is not reliable. You confirmed that hardened-sources-2.6.27-r7 without TOMOYO patch works fine. Will you try hardened-sources-2.6.27-r7 with TOMOYO patch? I think TOMOYO patch in ccs_hardened-sources r1 will be applicable for hardened-sources-2.6.27-r7 too. > allow read/write /virt/images/\*.img Please use "allow_read/write", not "allow read/write". Regards. _______________________________________________ tomoyo-users-en mailing list [email protected] http://lists.sourceforge.jp/mailman/listinfo/tomoyo-users-en
