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
| ||
|
Message-ID: <20080126191041.GA5233@lst.de> Date: Sat, 26 Jan 2008 20:10:41 +0100 From: Christoph Hellwig <hch@....de> To: Takashi Sato <t-sato@...jp.nec.com> Cc: Pekka Enberg <penberg@...helsinki.fi>, 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 On Fri, Jan 25, 2008 at 09:42:30PM +0900, Takashi Sato wrote: > 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? Given that XFS has implemented the ioctls for such a long time it might make more sense to simply move the ioctl implementation to fs/ioctl.c so it applies to all filesystem. No need to add a new syscall when the equivalent-functionality ioctls have to be supported forever anyway. - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists