| 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: Sun, 13 Apr 2008 10:04:02 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Bob Copeland <me@...copeland.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH 0/7] OMFS filesystem version 3 > Honestly, I'm not sure if this FS is mainline material or not. If it is, It looks mainline to me. It is far more relevant than most of the other file systems we support and it doesn't mess up core code at all. It's a loadable kernel module so the impact is basically nil, as well as being useful to other folk writing file systems. > Most of it was done by members of the ReplayTV community; I just used > their documentation. I'll see if I can get in touch with one of them to > see how they came up with that. I only figured out a few things, for > which I'd use the Karma as a black box for copying/deleting files etc. > and then poke at the resulting disk image with a hex editor. If you used their documentation and didn't do the reverse engineering or read any ReplayTV code there shouldn't be any problems. The big danger is if you reverse engineer their code and you write new code you may copy their implementation even accidentally (or be held to have done so). Alan -- 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