netdev - Re: [PATCH net-next 0/3] Make is_kdump_kernel() accessible from modules

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: <20140731.122244.665794236590108427.davem@davemloft.net>
Date:	Thu, 31 Jul 2014 12:22:44 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	vgoyal@...hat.com
Cc:	amirv@...lanox.com, andi@...stfloor.org, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, ogerlitz@...lanox.com,
	yevgenyp@...lanox.com
Subject: Re: [PATCH net-next 0/3] Make is_kdump_kernel() accessible from
 modules

From: Vivek Goyal <vgoyal@...hat.com>
Date: Thu, 31 Jul 2014 09:07:56 -0400

> If there are performance implications of low memory profile, then user
> needs to live with it. Otherwise they should not use low_memory_env
> boot option to begin with.

I personally think we should avoid changing scripts, by having a kdump
kernel force this low_mem profile to be true.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html