From: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, Eric Sandeen <sandeen@redhat.com>,
Josef Bacik <josef@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] fsfreeze: check ioctls
Date: Thu, 21 Jul 2011 11:32:15 +0900 [thread overview]
Message-ID: <1311215535.2763.20.camel@nausicaa> (raw)
The current fsfreeze API lacks a method to check the current freeze
status of a superblock. One might be tempted to think that a new vfs
ioctl is all we need, but with the current implemetation of fsfreeze it
it is possible to umount a freezed filesystem, which means that the only
way to check the freeze status is through the block device. For a moment
I thought I could get without the vfs version but then I realized that
the block device ioctl would not play well with btrfs.
Because of all of the above I ended up implementing both. Al also
suggested [1] a thaw-by-block-device ioctl which I am currently working
on.
[1] http://marc.info/?l=linux-kernel&m=125361768208298&w=2
next reply other threads:[~2011-07-21 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 2:32 Fernando Luis Vazquez Cao [this message]
2011-07-21 2:36 ` [PATCH 1/2] fsfreeze: add FIISFROZEN ioctl Fernando Luis Vazquez Cao
2011-07-21 2:41 ` [PATCH 2/2] fsfreeze: add BLKISFROZEN ioctl Fernando Luis Vazquez Cao
2011-07-27 7:30 ` [RFC][PATCH 0/4] fsfreeze: new API Fernando Luis Vazquez Cao
2011-07-27 7:32 ` [PATCH 1/4] fsfreeze: add vfs ioctl to check freeze state Fernando Luis Vazquez Cao
2011-07-27 7:34 ` [PATCH 2/4] fsfreeze: add block device " Fernando Luis Vazquez Cao
2011-07-27 7:35 ` [PATCH 3/4] fsfreeze: add ioctl to create a fd for freeze control Fernando Luis Vazquez Cao
2011-07-27 7:36 ` [PATCH 4/4] fsfreeze: add freeze fd ioctls Fernando Luis Vazquez Cao
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=1311215535.2763.20.camel@nausicaa \
--to=fernando@oss.ntt.co.jp \
--cc=hch@lst.de \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@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 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).