linux-kernel - Re: [2.6.30-rcX] Some ftrace debug option is consuming memory?

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200905270146.n4R1kjes036867@www262.sakura.ne.jp>
Date:	Wed, 27 May 2009 10:46:45 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:	rostedt@...dmis.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [2.6.30-rcX] Some ftrace debug option is consuming memory?

Steven Rostedt wrote:
> > I was running a VM with 1024MB of RAM.
> > 
> > I changed it to 512MB of RAM, and now I'm experiencing out of memory error.
> 
> How many virtual CPUs do you have configured?
> 
I assigned 2 virtual CPUs.
But this error occurs even with 1 virtual CPU.

> > 2.6.29.4 can boot with 512MB of RAM.
> > 2.6.30-rc1 and later cannot boot with 512MB of RAM if some debug options are
> > enabled.
> 
> Did 29.4 have tracing enabled and still worked?
> 
Yes.
Config (with all tracing options enabled) is at http://I-love.SAKURA.ne.jp/tmp/config-2.6.29.4-ok
Full log is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.29.4-ok-512MB.txt



> > < # CONFIG_IRQSOFF_TRACER is not set
> > < # CONFIG_SYSPROF_TRACER is not set
> > < # CONFIG_SCHED_TRACER is not set
> 
> Can you also disable the above three and see if you still see problems?
> 
I disabled the above three.

  # diff config-2.6.30-rc7-ng .config
  4c4
  < # Mon May 25 13:28:39 2009
  ---
  > # Wed May 27 10:11:09 2009
  1528d1527
  < CONFIG_TRACER_MAX_TRACE=y
  1539,1541c1538,1540
  < CONFIG_IRQSOFF_TRACER=y
  < CONFIG_SYSPROF_TRACER=y
  < CONFIG_SCHED_TRACER=y
  ---
  > # CONFIG_IRQSOFF_TRACER is not set
  > # CONFIG_SYSPROF_TRACER is not set
  > # CONFIG_SCHED_TRACER is not set

But I'm still seeing the problem.
Full log which cannot boot is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.30-rc7-ng-512MB.txt
Full log which can boot is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.30-rc7-ng-1024MB.txt

Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/