linux-kernel - Re: Versioning file system

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: <OF7FA807A1.64C0D5AF-ON882572FE.0061B34C-882572FE.00628322@us.ibm.com>
Date:	Mon, 18 Jun 2007 10:56:05 -0700
From:	Bryan Henderson <hbryan@...ibm.com>
To:	Jack Stone <jack@...keye.stone.uk.eu.org>
Cc:	akpm@...ux-foundation.org, alan <alan@...eserver.org>,
	hpa@...or.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system

>The question remains is where to implement versioning: directly in
>individual filesystems or in the vfs code so all filesystems can use it?

Or not in the kernel at all.  I've been doing versioning of the types I 
described for years with user space code and I don't remember feeling that 
I compromised in order not to involve the kernel.

Of course, if you want to do it with snapshots and COW, you'll have to ask 
where in the kernel to put that, but that's not a file versioning 
question; it's the larger snapshot question.

--
Bryan Henderson                     IBM Almaden Research Center
San Jose CA                         Filesystems


-
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/