linux-kernel - Re: [patch] docs, debugfs: start explicit debugfs documentation

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]

Message-ID: <20180710064234.GA2053@kroah.com>
Date:   Tue, 10 Jul 2018 08:42:34 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     David Rientjes <rientjes@...gle.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Jonathan Corbet <corbet@....net>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch] docs, debugfs: start explicit debugfs documentation

On Mon, Jul 09, 2018 at 03:12:48PM -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2018 15:00:17 -0700 (PDT) David Rientjes <rientjes@...gle.com> wrote:
> 
> > There is no canonical location for debugfs docuemntation, so start one.

What is wrong with Documenation/filesystems/debugfs.txt?

> > This is primarily motivated to describe the oom_free_timeout_ms interface
> > but it is extended for all the debugfs files that I am personally
> > interested in.
> > 
> > Hopefully this can be expanded in the future for better insight into how
> > the various interfaces can be used.

Ah, you are talking about the contents of debugfs files, right?  Just
use Documenation/ABI/ if you really want to document these things.  But
really, it's debugfs, so things can, and will, change, you should never
build tools that rely on the specific information contained in those
files.

thanks,

greg k-h