| 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: Thu, 7 May 2009 22:35:18 +0200 From: Pavel Machek <pavel@....cz> To: David Rientjes <rientjes@...gle.com> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Andrew Morton <akpm@...ux-foundation.org>, fengguang.wu@...el.com, linux-pm@...ts.linux-foundation.org, torvalds@...ux-foundation.org, jens.axboe@...cle.com, alan-jenkins@...fmail.co.uk, linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org Subject: Re: [PATCH 1/5] mm: Add __GFP_NO_OOM_KILL flag On Thu 2009-05-07 13:25:06, David Rientjes wrote: > On Thu, 7 May 2009, Rafael J. Wysocki wrote: > > > OK, let's try with __GFP_NO_OOM_KILL first. If there's too much disagreement, > > I'll use the freezer-based approach instead. > > > > Third time I'm going to suggest this, and I'd like a response on why it's > not possible instead of being ignored. > > All of your tasks are in D state other than kthreads, right? That means > they won't be in the oom killer (thus no zones are oom locked), so you can > easily do this Well, OOM killer may be running on behalf of some kthread at that point....? Quite unlikely, but possible AFAICT. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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