linux-kernel - Re: sched.c: why -fno-omit-frame-pointer?

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] [day] [month] [year] [list]

Message-ID: <20070823113036.GA29740@elte.hu>
Date:	Thu, 23 Aug 2007 13:30:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Adrian Bunk <bunk@...nel.org>, linux-kernel@...r.kernel.org,
	Andreas Schwab <schwab@...e.de>,
	Alan Modra <alan@...uxcare.com.au>,
	David Mosberger-Tang <davidm@....hp.com>
Subject: Re: sched.c: why -fno-omit-frame-pointer?


* Andi Kleen <andi@...stfloor.org> wrote:

> Adrian Bunk <bunk@...nel.org> writes:
> > 
> > Is the -fno-omit-frame-pointer still required for some reason, or is 
> > this a relict that could be removed?
> 
> It's needed so that the WCHAN /proc display can backtrace one level up 
> out of schedule()

it's not just one level - we'll back out until we are in scheduler 
functions (up to 16 levels). So it will back out of io_schedule() and 
other functions as well.

	Ingo
-
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/