Hi Goldwyn, On Thu, 2016-04-28 at 21:01 -0500, Goldwyn Rodrigues wrote: > From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx> > > This is an effort to represent fs structures in terms of kobjects. > > The primary goal of this was to provide a mechanism for the filesystems > to provide feedback to userspace but grew more than that. > In case of errors users may fix errors and could schedule a > complete filesystem check at a later point of time. > ENOSPC errors could be automated to delete temporary files > etc. > > As a implementation example, I have changed ocfs2 to support the change, > though it is not completely feasible change because of the way ksets are > represented in kset, but it delivers the idea. > > Taking this forward may reduce the house-keeping tasks such as searching, > list handling and locking. One example shown here is the super_block > destruction using kobjects. Since most filesystems do represent their > structures in sysfs, this would consolidate individual representations > under the filesystem, hopefully reducing code. > > Let me know what you think about the idea. > You can register any attributes in sysfs. So, what do you suggest finally? What common scheme for all file systems do you suggest to use? Suppose, I didn't catch the idea. Did you invent sysfs itself? Could you describe your vision more clearly? The idea looks obscure right now, from my point of view. Thanks, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
