linux-kernel - Re: [RFC PATCH 0/8] backtrace/oops with source/line information

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: <4F9A413B.50704@gmail.com>
Date:	Fri, 27 Apr 2012 14:48:27 +0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Jason Wessel <jason.wessel@...driver.com>
CC:	linux-kernel@...r.kernel.org, mingo@...hat.com,
	masami.hiramatsu.pt@...achi.com, rusty@...tcorp.com.au
Subject: Re: [RFC PATCH 0/8] backtrace/oops with source/line information

On 04/21/2012 05:29 AM, Jason Wessel wrote:
>
> The key difference here is that you get the source line information in
> any kind of oops/panic/backtrace, including inside kernel modules.  Of
> course this comes at the expense of some memory you do not get to use
> because these tables have to get stored in a place that is accessible
> after a crash.  On a system with 4 gigs of ram however, the cost is
> nearly insignificant when you have to give up a few megs for the
> capability.  The idea is to make it a bit easier to just jump into a
> source tree without having to use any tools to decode the dump (which
> I know every kernel developer out there already has anwyay :-)

So is the vmlinux size, right?
--
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/