[tomoyo-dev-en 128] Re: Memory problem

アーカイブの一覧に戻る

Jamie Nguyen dysco****@gmail*****
Sat Feb 5 21:19:23 JST 2011


Tetsuo Handa <from-****@i-lov*****> wrote:
> Jamie Nguyen wrote:
>> I've experienced this problem a second time with all domains set to
>> profile=1. After killing ccs-editpolicy and running again, there
>> appear to be no problems.
>>
>> Any ideas on how to debug?
>
> Seems that memory in the userspace cannot be freed by some reason. I haven't
> encountered this problem. Can you describe environments (Debian Squeeze? KVM?
> x86_32 or x86_64 ?) and send me the kernel config file you used for building
> the kernel?

Even though this has happened twice, I unfortunately haven't succeeded
in reproducing the problem.

I am running Arch Linux x86_64 normally (not in virtualized environment).

$ uname -a
Linux myhost 2.6.37-ccs #1 SMP PREEMPT Thu Feb 3 09:37:22 GMT 2011
x86_64 Intel(R) Core(TM)2 Duo CPU T7250****@2***** GenuineIntel
GNU/Linux

Kernel config can be found here:

http://projects.archlinux.org/svntogit/packages.git/tree/kernel26/repos/core-x86_64/config.x86_64

Only difference is the CCS/TOMOYO options:

$ zcat /proc/config.gz | grep -e CCS -e TOMOYO
# CONFIG_SECURITY_TOMOYO is not set
CONFIG_CCSECURITY=y
# CONFIG_CCSECURITY_LKM is not set
# CONFIG_CCSECURITY_DISABLE_BY_DEFAULT is not set
# CONFIG_CCSECURITY_USE_EXTERNAL_TASK_SECURITY is not set
CONFIG_CCSECURITY_MAX_ACCEPT_ENTRY=2048
CONFIG_CCSECURITY_DEFAULT_LOADER="/sbin/ccs-init"
CONFIG_CCSECURITY_ALTERNATIVE_TRIGGER="/sbin/ccs-start"
CONFIG_CCSECURITY_BUILTIN_INITIALIZERS="/sbin/modprobe /sbin/hotplug"
CONFIG_CCSECURITY_MAX_AUDIT_LOG=1024




More information about the tomoyo-dev-en mailing list
アーカイブの一覧に戻る