LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Takashi Sato" <t-sato@yk.jp.nec.com>
To: "Christoph Hellwig" <hch@infradead.org>,
"Andreas Dilger" <adilger@sun.com>
Cc: "Theodore Tso" <tytso@MIT.EDU>, <linux-ext4@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] ext3 freeze feature
Date: Fri, 15 Feb 2008 20:51:15 +0900 [thread overview]
Message-ID: <79B050214DA541F9A8B193C7AACC3C7B@nsl.ad.nec.co.jp> (raw)
In-Reply-To: <20080208145911.GA4257@infradead.org>
Hi,
Christoph Hellwig wrote:
> On Fri, Feb 08, 2008 at 08:26:57AM -0500, Andreas Dilger wrote:
>> You may as well make the common ioctl the same as the XFS version,
>> both by number and parameters, so that applications which already
>> understand the XFS ioctl will work on other filesystems.
>
> Yes. In facy you should be able to lift the implementations of
> XFS_IOC_FREEZE and XFS_IOC_THAW to generic code, there's nothing
> XFS-specific in there.
According to Documentation/ioctl-number.txt,
XFS_IOC_XXXs (_IOWR('X', aa, bb)) are defined for XFS like below.
>From Documentation/ioctl-number.txt:
----------------------------------------------------------------------------
Code Seq# Include File Comments
========================================================
: :
'X' all linux/xfs_fs.h
----------------------------------------------------------------------------
So XFS_IOC_FREEZE and XFS_IOC_THAW cannot be lifted to generic code simply.
I think we should create new generic numbers for freeze and thaw
like FIBMAP as followings.
linux/fs.h:
#define FIFREEZE _IO(0x00,3)
#define FITHAW _IO(0x00,4)
And xfs_freeze calls XFS_IOC_FREEZE with a magic number 1, but what is 1?
Instead, I'd like the sec to timeout on freeze API in order to thaw
the filesystem automatically. It can prevent a filesystem from staying
frozen forever.
(Because a freezer may cause a deadlock by accessing the frozen filesystem.)
Any comments are very welcome.
Cheers, Takashi
next prev parent reply other threads:[~2008-02-15 11:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 10:59 Takashi Sato
2008-01-25 11:17 ` Pekka Enberg
2008-01-25 12:42 ` Takashi Sato
2008-01-26 5:17 ` David Chinner
2008-01-26 19:10 ` Christoph Hellwig
2008-01-25 12:18 ` Dmitri Monakhov
2008-01-25 13:33 ` Theodore Tso
2008-01-25 16:34 ` Eric Sandeen
2008-01-25 16:42 ` Theodore Tso
2008-02-02 13:52 ` Pavel Machek
2008-01-28 13:13 ` Takashi Sato
2008-02-01 3:03 ` Kazuto Miyoshi
2008-01-31 8:53 ` Daniel Phillips
2008-02-07 1:05 ` Takashi Sato
2008-02-08 10:48 ` Takashi Sato
2008-02-08 13:26 ` Andreas Dilger
2008-02-08 14:59 ` Christoph Hellwig
2008-02-15 11:51 ` Takashi Sato [this message]
2008-02-15 14:24 ` Eric Sandeen
2008-02-19 11:27 ` t-sato
2008-02-26 8:20 ` [RFC] ext3 freeze feature ver 0.2 Takashi Sato
2008-02-26 16:39 ` Eric Sandeen
2008-02-26 17:08 ` Andreas Dilger
2008-02-27 8:31 ` Takashi Sato
2008-03-07 9:13 ` [RFC] freeze feature ver 1.0 Takashi Sato
2008-02-16 13:25 ` [RFC] ext3 freeze feature Christoph Hellwig
2008-02-13 8:23 ` Takashi Sato
2008-01-26 5:35 ` David Chinner
2008-01-26 5:39 ` David Chinner
2008-01-28 13:07 ` Takashi Sato
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=79B050214DA541F9A8B193C7AACC3C7B@nsl.ad.nec.co.jp \
--to=t-sato@yk.jp.nec.com \
--cc=adilger@sun.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@MIT.EDU \
--subject='Re: [RFC] ext3 freeze feature' \
/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
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).