linux-kernel - Re: [ckrm-tech] [PATCH 0/5] Allow more than PAGESIZE data read in configfs

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: <20061014044015.GE16880@suse.de>
Date:	Fri, 13 Oct 2006 21:40:15 -0700
From:	Greg KH <gregkh@...e.de>
To:	Paul Jackson <pj@....com>
Cc:	Joel Becker <Joel.Becker@...cle.com>, matthltc@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [ckrm-tech] [PATCH 0/5] Allow more than PAGESIZE data read in configfs

On Thu, Oct 12, 2006 at 05:01:25PM -0700, Paul Jackson wrote:
> Underneath each of these filesystems, sysfs, configfs, cpuset, resource
> groups, ... it would seem ideal if we had a single kernel file system
> infrastructure.  Actually, we're only a half a layer from having that,
> with vfs.  It just takes a fair bit of glue to construct any of these
> file systems out of vfs primitives.

No, it's pretty small to create a ram-based filesystem these days.  Look
at securityfs and debugfs for two simple examples that you should copy
if you want to create your own.  If you can come up with ways of making
those files smaller, then that would be great.  But as it is, it is
_really_ simple to do this right now, especially with two working
examples to copy from :)

thanks,

greg k-h
-
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/