linux-kernel - [for-next][PATCH] tracing: Fix comments about tracefs

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

Message-ID: <20150209171226.48f42e69@gandalf.local.home>
Date:	Mon, 9 Feb 2015 17:12:26 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Namhyung Kim <namhyung@...nel.org>
Subject: [for-next][PATCH] tracing: Fix comments about tracefs

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 75c92ca0171ef419d62b16c0f5b0440d071b3b47


Steven Rostedt (Red Hat) (1):
      tracing: Fix comments about tracefs

----
 fs/tracefs/inode.c   | 8 +-------
 kernel/trace/trace.c | 2 +-
 2 files changed, 2 insertions(+), 8 deletions(-)
---------------------------
commit 75c92ca0171ef419d62b16c0f5b0440d071b3b47
Author: Steven Rostedt (Red Hat) <rostedt@...dmis.org>
Date:   Mon Feb 9 10:18:26 2015 -0500

    tracing: Fix comments about tracefs
    
    There were some typos and mistakes in the tracefs code and the code
    that calls tracefs.
    
    Link: http://lkml.kernel.org/r/20150209055619.GA30788@sejong
    
    Reported-by: Namhyung Kim <namhyung@...nel.org>
    Signed-off-by: Steven Rostedt <rostedt@...dmis.org>

diff --git a/fs/tracefs/inode.c b/fs/tracefs/inode.c
index d92bdf3b079a..f9adf6f86964 100644
--- a/fs/tracefs/inode.c
+++ b/fs/tracefs/inode.c
@@ -381,9 +381,6 @@ static struct dentry *end_creating(struct dentry *dentry)
  * pointer must be passed to the tracefs_remove() function when the file is
  * to be removed (no automatic cleanup happens if your module is unloaded,
  * you are responsible here.)  If an error occurs, %NULL will be returned.
- *
- * If tracefs is not enabled in the kernel, the value -%ENODEV will be
- * returned.
  */
 struct dentry *tracefs_create_file(const char *name, umode_t mode,
 				   struct dentry *parent, void *data,
@@ -450,9 +447,6 @@ static struct dentry *__create_dir(const char *name, struct dentry *parent,
  * This function will return a pointer to a dentry if it succeeds.  This
  * pointer must be passed to the tracefs_remove() function when the file is
  * to be removed. If an error occurs, %NULL will be returned.
- *
- * If tracing is not enabled in the kernel, the value -%ENODEV will be
- * returned.
  */
 struct dentry *tracefs_create_dir(const char *name, struct dentry *parent)
 {
@@ -470,7 +464,7 @@ struct dentry *tracefs_create_dir(const char *name, struct dentry *parent)
  *
  * The instances directory is special as it allows for mkdir and rmdir to
  * to be done by userspace. When a mkdir or rmdir is performed, the inode
- * locks are released and the methhods passed in (@mkdir and @rmdir) are
+ * locks are released and the methods passed in (@mkdir and @rmdir) are
  * called without locks and with the name of the directory being created
  * within the instances directory.
  *
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 3c8913bac204..89755e0df8eb 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -6515,7 +6515,7 @@ struct dentry *tracing_init_dentry(void)
 	 * As there may still be users that expect the tracing
 	 * files to exist in debugfs/tracing, we must automount
 	 * the tracefs file system there, so older tools still
-	 * work with the newer kerenl.
+	 * work with the newer kernel.
 	 */
 	tr->dir = debugfs_create_automount("tracing", NULL,
 					   trace_automount, NULL);
--
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/