linux-kernel - Re: [PATCH 1/2] KDB: Make LINES an internal variable.

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]

Date:	Fri, 24 Feb 2012 19:17:56 -0800 (PST)
From:	Andrei Warkentin <awarkentin@...are.com>
To:	linux-kernel@...r.kernel.org
Cc:	jason wessel <jason.wessel@...driver.com>,
	kgdb-bugreport@...ts.sourceforge.net
Subject: Re: [PATCH 1/2] KDB: Make LINES an internal variable.

Hi,

----- Original Message -----
> From: "Andrei Warkentin" <andreiw@...are.com>
> To: kgdb-bugreport@...ts.sourceforge.net
> Cc: linux-kernel@...r.kernel.org, "jason wessel" <jason.wessel@...driver.com>, andreiw@...are.com
> Sent: Friday, February 17, 2012 9:07:15 PM
> Subject: [PATCH 1/2] KDB: Make LINES an internal variable.
> 
> 1) If you run 'dumpall', LINES will remain set to
>    10000, and you might wonder why dmesg now doesn't
>    page.
> 2) If you run any command that sets LINES, you will
>    eventually exhaust the heap.
> 
> To address (1), you can save and restore across
> calls to "defcmd" commands, which might contain
> "set LINES". This becomes awkward with keeping
> LINES in env, but there is no real reason why
> LINES cannot be treated as an internal variable.
> Additionally, you get rid of the (small) kdb heap
> usage for LINES.
> 

Does any of this make sense :-)?

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