[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0712271222190.31582@schroedinger.engr.sgi.com>
Date: Thu, 27 Dec 2007 12:28:14 -0800 (PST)
From: Christoph Lameter <clameter@....com>
To: Al Viro <viro@...IV.linux.org.uk>
cc: Theodore Tso <tytso@....edu>, Andi Kleen <andi@...stfloor.org>,
Willy Tarreau <w@....eu>, Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@...radead.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: SLUB sysfs support
Hmmm.. If I separately allocate the kobject then I can no longer get to
the kmem_cache structure from the kobject.
I need to add a second kobject_del to sysfs_slab_remove() to make sysfs
completely forget about the object?
Probably should track down any remaining symlinks at that point and nuke
them too. Isnt there some way to convince sysfs to remove the symlinks
if the target vanishes?
--
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