linux-kernel - Re: [RFC] ext3 freeze feature

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <001c01c85f4f$bfd128f0$41a8400a@bsd.tnes.nec.co.jp>
Date:	Fri, 25 Jan 2008 21:42:30 +0900
From:	"Takashi Sato" <t-sato@...jp.nec.com>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	<linux-ext4@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, "Christoph Hellwig" <hch@....de>
Subject: Re: [RFC] ext3 freeze feature

Hi,

> I am also wondering whether we should have system call(s) for these:
> 
> On Jan 25, 2008 12:59 PM, Takashi Sato <t-sato@...jp.nec.com> wrote:
>> +       case EXT3_IOC_FREEZE: {
> 
>> +       case EXT3_IOC_THAW: {
> 
> And just convert XFS to use them too?

I think it is reasonable to implement it as the generic system call, as you said.
Does XFS folks think so?

Cheers, Takashi
--
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/