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
| ||
|
Date: Mon, 15 Sep 2008 01:21:39 -0700 From: Daniel Phillips <phillips@...nq.net> To: tux3@...3.org Cc: linux-kernel@...r.kernel.org Subject: Tux3 Report: What next? Hi all, It's been a busy week with all the checkins. Not all of them from me! And Tux3 university, which seems to be going quite well. For the next session (Tuesday, 8 p.m. pacific time on irc.oftc.net #tux3) the theme will be: VFS read and write. Yes, that's all, and it's a lot. So getting xattrs working took a week, and it was quite a week with all the design introspection about atoms and such. In the end, the design came out really nice and I guess we are going to be able to go with our hoped for no-compromise solution: we translate xattr names into atoms and refcount the atoms persistently, and do it all at close to the speed we would get from just storing the xattr names as ascii strings, per inode. According to my calculations anyway. We will have to wait for something closer to production code before we can really measure it, and I am presuming that there will be a little more work done to put a simple cache, like a hash table, in front of the atom machinery. An unexpected spinoff benefit of the atom work is, we now have a really nice generic mechanism for implementing de-duplication, which work will be attempted by an enthusiastic team of volunteers, as a university project. I expect we will hear more on that soon. Now that question again: what next? Big items still outstanding to get to proof of concept: 1) Atomic commit 2) Versioning 3) Extents 4) Kernel port The kernel port is underway, it started yesterday when Maciej decided to barge in and implement his "junkfs", which as I understand it, is fearlessly attempting to load a superblock at the moment. Not one to be left behind, I checked in a stub Tux3 filesystem to a new Git repo, which I hope is going to become a real Tux3 filesystem in the not too distant future: http://phunq.net/tux3fs/ And our fuse porters have been busy, with xattr support checked in by Tero, mere hours after my first shaky prototype landed. Well, I am so happy with the way things are going in userspace that I plan to stay there a while longer. It is pretty much a coin toss which of the three non-kernel projects to jump into, so I choose versioning. Versioning is, after all, the main reason this project exists. In other news, it is getting close to Halloween, and that means getting close to Tux3 Cabal party time. More on that later. As always, everyone is welcome to jump in and join the development party, it's fun: http://tux3.org/ Regards, Daniel -- 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