linux-kernel - Re: [PATCH] x86: Fix memory leak of init_vdso

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: <CAEQi4bfm7zp-Lq-Hn8JD7Dq7fOzyt2-X9Kk_jB07S_S55uC81w@mail.gmail.com>
Date:	Mon, 11 Jul 2011 11:23:48 +0800
From:	wzt wzt <wzt.wzt@...il.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Michal Hocko <mhocko@...e.cz>, mingo@...hat.com,
	linux-kernel@...r.kernel.org, x86@...nel.org, tglx@...utronix.de,
	hpa@...or.com
Subject: Re: [PATCH] x86: Fix memory leak of init_vdso_vars()

maybe, we can just panic() when kmalloc failed instead of add a new GFP_PANIC.

new patch will coming soon.

On Fri, Jul 8, 2011 at 2:33 AM, Andi Kleen <ak@...ux.intel.com> wrote:
> When you run out of memory at early system boot (this is early
> system boot only) the system is toast anyways. There's no way
> to recover.
>
> I would just add a few GFP_PANICs and then drop the error paths.
>
> -Andi
>
>
--
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/