From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Stornelli Subject: Re: BUG: enabling psacct breaks fsfreeze Date: Sat, 03 Nov 2012 09:22:38 +0100 Message-ID: <5094D44E.8030808@gmail.com> References: <20121023094351.GC27919@pcnci.linuxbox.cz> <20121031121517.GD18424@quack.suse.cz> <20121031124600.GM20752@pcnci.linuxbox.cz> <20121101093723.GC6584@quack.suse.cz> <20121101111957.GD6584@quack.suse.cz> <20121101142325.GD20752@pcnci.linuxbox.cz> <20121101225053.GB31937@quack.suse.cz> <5093977A.9010507@gmail.com> <20121102104018.GG20752@pcnci.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kara , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Nikola Ciprich Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:47097 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752826Ab2KCI3P (ORCPT ); Sat, 3 Nov 2012 04:29:15 -0400 In-Reply-To: <20121102104018.GG20752@pcnci.linuxbox.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Il 02/11/2012 11:40, Nikola Ciprich ha scritto: >> I saw this behavior (task-hang) when I tested the fsfreeze code. I was >> writing a little patch to replace fsfreeze's wait queue with a killable >> queue, in this way the user can do at least "kill -9", but since the >> behavior was the same before your patch I didn't send it. I don't know if we >> can break any previous behavior. The funny thing here is that it's like if >> fsfreeze freezes itself :) > > I think freezing all tasks ain't that bad, my problem is it's not possible to > start fsfreeze -u to thaw filesystem.. > > Yes, of course. It was only a general comment. Marco