linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: enabling psacct breaks fsfreeze
Date: Sat, 03 Nov 2012 09:22:38 +0100	[thread overview]
Message-ID: <5094D44E.8030808@gmail.com> (raw)
In-Reply-To: <20121102104018.GG20752@pcnci.linuxbox.cz>

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

  reply	other threads:[~2012-11-03  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23  9:43 BUG: enabling psacct breaks fsfreeze Nikola Ciprich
2012-10-31 12:15 ` Jan Kara
2012-10-31 12:46   ` Nikola Ciprich
2012-11-01  9:37     ` Jan Kara
2012-11-01 11:19       ` Jan Kara
2012-11-01 14:23         ` Nikola Ciprich
2012-11-01 22:50           ` Jan Kara
2012-11-02  9:50             ` Marco Stornelli
2012-11-02 10:40               ` Nikola Ciprich
2012-11-03  8:22                 ` Marco Stornelli [this message]
2012-11-07 18:51             ` Jan Kara
2012-11-07 21:21               ` Nikola Ciprich
2012-11-07 22:32                 ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5094D44E.8030808@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).