[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080216132502.GB1344@infradead.org>
Date: Sat, 16 Feb 2008 08:25:02 -0500
From: Christoph Hellwig <hch@...radead.org>
To: Takashi Sato <t-sato@...jp.nec.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Andreas Dilger <adilger@....com>, Theodore Tso <tytso@....EDU>,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] ext3 freeze feature
On Fri, Feb 15, 2008 at 08:51:15PM +0900, Takashi Sato wrote:
> 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
Actually we've lifted specific ioctls to the generic layer before all
the time in drivers. That's the only way to make functionality that was
specific to a single driver (or in this case filesystem) generic. If
the numbering issues confuses you make sure to add a big comment
describing it
> And xfs_freeze calls XFS_IOC_FREEZE with a magic number 1, but what is 1?
As Eric said it's ignored.
> 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.)
Timeout based locking is generally a horrible idea, there's a reason
we don't have any primitives for that in the kernel :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists