From: Dave Chinner <david@fromorbit.com>
To: "Fernando Luis Vázquez Cao" <fernando_b1@lab.ntt.co.jp>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Ingo Molnar <mingo@redhat.com>,
Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fsfreeze: tell hung_task about processes put to sleep
Date: Sat, 13 Oct 2012 12:06:13 +1100 [thread overview]
Message-ID: <20121013010613.GP2739@dastard> (raw)
In-Reply-To: <1350035252.6500.2.camel@nexus.lab.ntt.co.jp>
On Fri, Oct 12, 2012 at 06:47:32PM +0900, Fernando Luis Vázquez Cao wrote:
> Any process attempting to write to a frozen filesystem uninterruptibly and
> unkillably waits for the filesystem to be thawed. This wait is of unbounded
> length. Ignore such waits in the hung_task detector.
Filesystems should not be frozen for long enough to trigger the hung
task detector under normal usage. IMO, if you are freezing a
filesystem for that long, then you're either doing something wrong
or something has gone wrong, and in either case I think we should be
emitting warnings...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-13 1:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 9:47 [PATCH] fsfreeze: tell hung_task about processes put to sleep Fernando Luis Vázquez Cao
2012-10-13 1:06 ` Dave Chinner [this message]
2012-10-15 3:24 ` Fernando Luis Vazquez Cao
2012-10-15 6:36 ` Dave Chinner
2012-10-15 6:51 ` Fernando Luis Vazquez Cao
2012-10-15 21:02 ` Dave Chinner
2012-10-16 2:30 ` Fernando Luis Vazquez Cao
2012-10-16 4:52 ` Dave Chinner
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=20121013010613.GP2739@dastard \
--to=david@fromorbit.com \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.