| 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
| ||
|
Message-ID: <BANLkTino+9_GEb28gfZYSu-R0JW44M1mqQ@mail.gmail.com> Date: Tue, 26 Apr 2011 11:19:22 +0800 From: Dave Young <hidave.darkstar@...il.com> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] use oom_killer_disabled in all oom pathes On Tue, Apr 26, 2011 at 11:14 AM, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote: >> On Tue, Apr 26, 2011 at 10:57 AM, KOSAKI Motohiro >> <kosaki.motohiro@...fujitsu.com> wrote: >> >> oom_killer_disable should be a global switch, also fit for oom paths >> >> other than __alloc_pages_slowpath >> >> >> >> Here add it to mem_cgroup_handle_oom and pagefault_out_of_memory as well. >> > >> > Can you please explain more? Why should? Now oom_killer_disabled is used >> > only hibernation path. so, Why pagefault and memcg allocation will be happen? >> >> Indeed I'm using it in virtio balloon test, oom killer triggered when >> memory pressure is high. >> >> literally oom_killer_disabled scope should be global, isn't it? > > ok. virtio baloon seems fair usage. if you add new usage of oom_killer_disabled > into the patch description, I'll ack this one. Thanks, then I will resend the virtio balloon patch along with this. -- Regards dave -- 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/
Powered by blists - more mailing lists