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
| ||
|
Date: Sun, 7 Dec 2014 08:59:40 -0500 From: Tejun Heo <tj@...nel.org> To: Michal Hocko <mhocko@...e.cz> Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, "\\\"Rafael J. Wysocki\\\"" <rjw@...ysocki.net>, David Rientjes <rientjes@...gle.com>, Johannes Weiner <hannes@...xchg.org>, Oleg Nesterov <oleg@...hat.com>, Cong Wang <xiyou.wangcong@...il.com>, LKML <linux-kernel@...r.kernel.org>, linux-pm@...r.kernel.org Subject: Re: [PATCH -v2 2/5] OOM: thaw the OOM victim if it is frozen On Sun, Dec 07, 2014 at 11:45:39AM +0100, Michal Hocko wrote: .... > void mark_tsk_oom_victim(struct task_struct *tsk) > { > set_tsk_thread_flag(tsk, TIF_MEMDIE); > + __thaw_task(tsk); Yeah, this is a lot better. Maybe we can add a comment at least pointing readers to where to look at to understand what's going on? This stems from the fact that OOM killer which essentially is a memory reclaim operation overrides freezing. It'd be nice if that is documented somehow. Thanks. -- tejun -- 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