linux-kernel - [PATCH 0/3] Allow sysfs to be dynamically populated

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-next>] [day] [month] [year] [list]

Message-ID: <20091020054740.GC29158@parisc-linux.org>
Date:	Mon, 19 Oct 2009 23:47:40 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Greg Kroah-Hartman <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-pci@...r.kernel.org
Subject: [PATCH 0/3] Allow sysfs to be dynamically populated

The first patch in this series is just a bugfix.

The second and third patches offer progressively more flexibility to
dynamically construct the contents of sysfs directories.  The second
patch delays the allocation of sysfs_dirents until the contents of
the directory is requested.  This functionality is only used by the
attribute_groups in that patch, but could (in principle) be extended to
other directory providers.

The third patch extends this to permit attribute groups to be dynamically
constructed before the directory they're in is populated.  I also add a
user for this; the much-requested ability to display the MSI-X vectors
in use by a device.

Both patches also deconstruct the directories / attribute groups when the
dentry of the directory goes out of cache.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/