From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753043AbbJaI5k (ORCPT ); Sat, 31 Oct 2015 04:57:40 -0400 Received: from mx2.suse.de ([195.135.220.15]:57664 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752501AbbJaI5h (ORCPT ); Sat, 31 Oct 2015 04:57:37 -0400 Message-ID: <1446281756.21651.7.camel@suse.com> Subject: Re: [PATCH 1/3] power, vfs: move away from PF_KTHREAD freezing in favor of fs freezing From: Oliver Neukum To: Jiri Kosina Cc: "Rafael J. Wysocki" , Dave Chinner , Jan Kara , Christoph Hellwig , Linus Torvalds , Al Viro , Tejun Heo , Pavel Machek , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-pm@vger.kernel.org Date: Sat, 31 Oct 2015 09:55:56 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2015-10-30 at 14:47 +0100, Jiri Kosina wrote: > Basically the main argument why kthread freezer is not needed boils > down to > this: the only facility that is needed during suspend: "no persistent > fs > changes are allowed from now on". Is that true? Drivers of character devices also may assume that IO and suspend() wouldn't race (except in fairly clear exceptions) Regards Oliver