linux-kernel - Re: [PATCHSET v2] sysfs: use seq_file and unify regular and bin file handling

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: <20131007170005.GB2481@htj.dyndns.org>
Date:	Mon, 7 Oct 2013 13:00:05 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	kay@...y.org, linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	bhelgaas@...gle.com
Subject: Re: [PATCHSET v2] sysfs: use seq_file and unify regular and bin file
 handling

Hello,

On Sat, Oct 05, 2013 at 05:40:32PM -0700, Greg KH wrote:
> > * 0001-0008 are the same as before.
> 
> Nice, I've applied all of these now.

Great!

> How are you going to use sysfs from another kernel subsystem?  Is this
> for another filesystem, or do you want to use kobjects for some other
> subsystem that doesn't export them using sysfs?

I was at first trying to convert sysfs interface to not use kobject
but that caused too much disruption and I'm now trying to separate out
the core functionality into a separate filesystem - currently named
kernfs, so sysfs will be a consumer of kernfs translating between
kobject and kernfs interface, and cgroup will be the second user which
replaces its own pseudo filesystem implementation with kernfs.

Thanks a lot.

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