Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759251AbbGHViT (ORCPT ); Wed, 8 Jul 2015 17:38:19 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:45855 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758637AbbGHViP (ORCPT ); Wed, 8 Jul 2015 17:38:15 -0400 From: "Rafael J. Wysocki" To: Alan Stern Cc: Pavel Machek , Oliver Neukum , Dave Chinner , Henrique de Moraes Holschuh , Len Brown , Len Brown , One Thousand Gnomes , "linux-kernel@vger.kernel.org" , Linux PM list Subject: Re: [PATCH 1/1] suspend: delete sys_sync() Date: Thu, 09 Jul 2015 00:04:43 +0200 Message-ID: <2508991.dbxJnzl9vM@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/4.1.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1902 Lines: 50 On Wednesday, July 08, 2015 10:40:00 AM Alan Stern wrote: > On Wed, 8 Jul 2015, Pavel Machek wrote: > > > > well, that depends on what the purpose of the sync is supposed to be. > > > > > > If it is there to prevent users from corrupting their filesystems as a result > > > of a mistake, it is insufficient. If it's there for other reasons, I'm wondering > > > what those reasons are (on systems that suspend and resume reliably, because the > > > original reason to put it in there was to reduce the damage from suspend/resume > > > crashes). > > > > I put it there, and there were more reasons than "crashes" to put it > > there. > > > > 1) crashes. > > > > 2) battery is quite likely to run out in suspended machine. > > > > 3) if someone pulls the stick and puts it in other machine, I wanted > > consistent filesystem at least after journal replay. > > I was going to make the same points. > > From my point of view, whether to issue a sync is a tradeoff. I can't > remember any time in the last several years where lack of a sync would > have caused a problem for my computers, but the possibility still > exists. > > So on one hand, issuing the sync can help prevent a low-probability > problem. On the other hand, issuing the sync takes a small amount of > time (negligible for my purposes but not negligible for Len and > others). > > I prefer to pay a very small cost to prevent a low-probability problem. > Others may not want to pay, because to them the cost is larger or the > probability is lower. > > _That_ is the justification for not eliminating the sync completely but > making it optional. Agreed. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/