linux-kernel - Re: Subject: [PATCHSET driver-core-next] sysfs: separate out kernfs, part #1

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]

Date:	Tue, 29 Oct 2013 15:29:50 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	kay@...y.org, linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	bhelgaas@...gle.com
Subject: Re: Subject: [PATCHSET driver-core-next] sysfs: separate out kernfs,
 part #1

On Thu, Oct 24, 2013 at 11:49:06AM -0400, Tejun Heo wrote:
> Hello,
> 
> This patchset contains 34 patches to separate out core sysfs features
> into kernfs.  kernfs exclusively deals with sysfs_dirent, which will
> be later renamed to kernfs_node, and kernfs_ops.  sysfs becomes a
> wrapping layer over sysfs which interfaces kobject and
> [bin_]attribute.
> 
> The goal of these changes is to allow other users to make use of the
> core features of sysfs instead of rolling their own pseudo filesystem
> implementation which usually fails to deal with issues with file
> shutdowns, locking separation from vfs layer and so on.  This patchset
> refactors sysfs and separates out most core functionalities to kernfs;
> however, the mount code hasn't been updated yet and it can't be used
> by other users yet.  The patchset is pretty big already and the two
> steps can be separated relatively well, so I think this is a good
> split point.

I've applied the first 6 patches here, as they only did cleanup stuff.
As it's late in the development cycle (i.e. 3.12 is going to be out in
days), I'd prefer to wait on the rest until 3.13-rc1 is out so that it
gets lots of testing in linux-next.

So, I'll hold off on the rest of these until then, ok?

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/