linux-kernel - Re: ODEBUG: Out of memory. ODEBUG disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5c3b1cf4-1d83-c0a5-4243-28fde66b5cd9@linux.alibaba.com>
Date:   Fri, 9 Nov 2018 13:42:24 -0800
From:   Yang Shi <yang.shi@...ux.alibaba.com>
To:     Qian Cai <cai@....us>, open list <linux-kernel@...r.kernel.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Waiman Long <longman@...hat.com>,
        Arnd Bergmann <arnd@...db.de>,
        "Joel Fernandes (Google)" <joel@...lfernandes.org>,
        Zhong Jiang <zhongjiang@...wei.com>
Subject: Re: ODEBUG: Out of memory. ODEBUG disabled



On 11/9/18 1:36 PM, Qian Cai wrote:
> It is a bit annoying on this aarch64 server with 64 CPUs that is
> booting the latest mainline (3541833fd1f2) causes object debugging
> always running out of memory.

May you please paste the detail failure log?

>
> I have to boot the kernel with only 16 CPUs instead (nr_cpus=16)
> to make it work. Is it expected that object debugging is not going
> to work with large machines?

I don't think so. I'm supposed it works well with large CPU number on x86.

Thanks,
Yang