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, 3 May 2009 11:47:18 +0200 From: Pavel Machek <pavel@....cz> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Andrew Morton <akpm@...ux-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, linux-pm@...ts.linux-foundation.org Subject: Re: [PATCH 1/3] PM: Disable OOM killer during system-wide power transitions > > Does the same apply to suspending? If so, why? > > Because I think it doesn't work anyway. User space processes are frozen and > effectively in TASK_UNINTERRUPTIBLE, so they won't be killed. > > > I think this is an OK change, as long as the only thing which is > > allocating memory is hibernation itself. If random processes are still > > doing random memory allocations at this time then their failed memory > > allocation could be just as fatal as an oom-killing. Moreso if they're > > s/bin/init or whatever. > > At this point all of the user space tasks are frozen. Well, many kernel threads still remain active. But it is true that OOM killer is unlikely to help. 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