From: Jan Kara <jack@suse.cz>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [TOPIC] Filesystem freezing
Date: Tue, 27 Mar 2012 22:26:20 +0200 [thread overview]
Message-ID: <20120327202620.GG5020@quack.suse.cz> (raw)
Hello,
in last month or two I've been working on making filesystem freezing work
reliably (avoid dirty data on frozen filesystem, avoid all sorts of
deadlocks, etc.). This effort seems to be slowly comming to an end so I can
be giving a heads up to filesystem developers about current state:
what happens in VFS, what filesystems may need to do, what they need not
do. Also I'd like to hear back if some filesystem has problem with the
new design or other feedback.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
reply other threads:[~2012-03-27 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120327202620.GG5020@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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).