| 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, 24 Nov 2013 09:28:22 -0500 From: Tejun Heo <tj@...nel.org> To: Christoph Hellwig <hch@...radead.org> Cc: gregkh@...uxfoundation.org, kay@...y.org, linux-kernel@...r.kernel.org, ebiederm@...ssion.com, bhelgaas@...gle.com Subject: Re: [PATCHSET driver-core-next] sysfs: separate out kernfs, take #3 Hello, On Sun, Nov 24, 2013 at 01:16:02AM -0800, Christoph Hellwig wrote: > It would be highly useful if you could explain us what kernfs is > supposed to do and why we're cheerfully waiting for it. Also given Oops, sorry about that. It was explained in earlier series but I probably should carry on a simplified explanation on later ones too. It's just separating out the core features of sysfs into a separate filesystem so that it can be used by non-kobject based users too. So, kernfs implements the core pseudo file functionality and sysfs becomes kobject-wrapping layer on top of it. I'm gonna convert cgroup to use kernfs and Greg seems to have some plans for debugfs, IIUC. > that you touch VFS core files please Cc linux-fsdevel for those and > explain them in detail. Does it? Ah, okay, fs/Makefile and fs/namespace.c. The former is just adding kernfs/ directory and the latter is splitting out kernfs_init() from sysfs_init() call. Both are trivial. Will cc linux-fsdevel on those patches. Thanks. -- tejun -- 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