| 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: <50885B2E.5050500@linux.vnet.ibm.com> Date: Wed, 24 Oct 2012 14:18:38 -0700 From: Dave Hansen <dave@...ux.vnet.ibm.com> To: Borislav Petkov <bp@...en8.de>, Andrew Morton <akpm@...ux-foundation.org>, Michal Hocko <mhocko@...e.cz>, linux-mm@...ck.org, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] add some drop_caches documentation and info messsge On 10/24/2012 02:06 PM, Borislav Petkov wrote: > On Wed, Oct 24, 2012 at 01:48:36PM -0700, Andrew Morton wrote: >> Well who knows. Could be that people's vm *does* suck. Or they have >> some particularly peculiar worklosd or requirement[*]. Or their VM >> *used* to suck, and the drop_caches is not really needed any more but >> it's there in vendor-provided code and they can't practically prevent >> it. > > I have drop_caches in my suspend-to-disk script so that the hibernation > image is kept at minimum and suspend times are as small as possible. > > Would that be a valid use-case? Sounds fairly valid to me. But, it's also one that would not be harmed or disrupted in any way because of a single additional printk() during each suspend-to-disk operation. -- 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