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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1549900.RSMcUBBPG7@vostro.rjw.lan>
Date:	Sat, 01 Aug 2015 01:57:44 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 1/1] suspend: make sync() on suspend-to-RAM build-time optional

On Friday, July 31, 2015 12:46:17 PM Len Brown wrote:
> From: Len Brown <len.brown@...el.com>
> 
> The Linux kernel suspend path has traditionally invoked sys_sync()
> before freezing user threads.
> 
> But sys_sync() can be expensive, and some user-space OS's do not want
> the kernel to pay the cost of sys_sync() on every suspend -- preferring
> invoke sync() from user-space if/when they want it.
> 
> So make sys_sync on suspend build-time optional.
> 
> The default is unchanged.
> 
> Signed-off-by: Len Brown <len.brown@...el.com>

OK, I'm replacing your previous sync patch with this one (modulo some minor
changes in the help text).

Thanks,
Rafael

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ