On Wed, Aug 31, 2016 at 04:38:16PM -0500, Eric Sandeen wrote: > On 8/31/16 2:08 PM, David Sterba wrote: > > On Wed, Aug 31, 2016 at 10:13:49AM -0500, Eric Sandeen wrote: > >> A /sys/kernel/debug/btrfs/test file was added nearly > >> two and a half years ago, but it serves no purpose; > > > > It does. Introduced in 1bae30982bc86ab66d61ccb6e22792593b45d44d says > > something about helping developers to easily export information from the > > filesystem, to aid debugging. Writing the debugfs support code is not > > obviously trivial, so it's idling in the source. Exporing a new value is > > as easy as copy and update 3 lines of code. If you have no use for it, > > fine. > > I had thought that Documentation/filesystems/debugfs.txt would suffice, > but if you keep stuff lying around in btrfs just in case somebody needs > to export a global variable in the future, I suppose that's cool too. ;)
How much time would you spend coding it? I guess more than a couple of minutes, possibly more than once. And not in the middle of debugging something else. There are more examples of code that has no apparent user but is used for debugging. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
