All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] ftrace: add an fsync tracer
Date: Wed, 5 Nov 2008 20:43:31 +0100	[thread overview]
Message-ID: <20081105194326.GA5839@joi> (raw)
In-Reply-To: <20081105094902.27ec4b39@infradead.org>

On Wed, Nov 05, 2008 at 09:49:02AM -0800, Arjan van de Ven wrote:
> --- /dev/null
> +++ b/kernel/trace/trace_fsync.c
> @@ -0,0 +1,165 @@
> +/*
> + * trace fsync calls
> + * Copyright (C) 2008 Intel Corporation
> + *
> + * Based extensively on trace_sched_switch.c
> + * Copyright (C) 2007 Steven Rostedt <srostedt@redhat.com>
> + *
> + */
> +#include <linux/module.h>
> +#include <linux/fs.h>
> +#include <linux/debugfs.h>
> +#include <linux/kallsyms.h>
> +#include <linux/uaccess.h>
> +#include <linux/ftrace.h>
> +#include <trace/fs.h>
> +
> +#include "trace.h"
> +
> +static struct trace_array	*ctx_trace;
> +static int __read_mostly	tracer_enabled;
> +static atomic_t			fsync_ref;
> +
> +static void
> +probe_do_fsync(struct file *file, int datasync)
> +{
> +	char *buffer;
> +	char *err;
> +
> +	if (!atomic_read(&fsync_ref))
> +		return;
> +
> +	if (!tracer_enabled)
> +		return;
> +
> +	buffer = kmalloc(4096, GFP_KERNEL);
> +	if (!buffer)
> +		return;
> +
> +	memset(buffer, 0, 4096);

kzalloc?

> +	err = d_path(&file->f_path, buffer, 4096);
> +
> +	if (IS_ERR(err))
> +		goto out;
> +
> +	ftrace_printk("Process %s is calling fsync on %s\n",
> +			current->comm, err);

err? not buffer?

> +
> +out:
> +	kfree(buffer);
> +}
> +
> (...)

  reply	other threads:[~2008-11-05 19:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 17:49 [PATCH] ftrace: add an fsync tracer Arjan van de Ven
2008-11-05 19:43 ` Marcin Slusarz [this message]
2008-11-05 20:36   ` Arjan van de Ven
2008-11-06  7:20     ` Ingo Molnar
2008-11-06 12:55 ` Peter Zijlstra
2008-11-06 13:28   ` Frédéric Weisbecker
2008-11-06 14:06   ` Arjan van de Ven
2008-11-06 14:19     ` Peter Zijlstra
2008-11-06 14:31       ` Arjan van de Ven
2008-11-06 14:50         ` Peter Zijlstra
2008-11-06 15:01           ` Arjan van de Ven
2008-11-06 15:34             ` Steven Rostedt
2008-11-06 17:45               ` Arjan van de Ven
2008-11-06 20:19                 ` Frank Ch. Eigler
2008-11-06 20:29                   ` Peter Zijlstra
2008-11-06 20:57                     ` Frank Ch. Eigler
2008-11-06 21:18                     ` Jason Baron
2008-11-06 21:53                     ` Mathieu Desnoyers
2008-11-06 22:14                       ` Frank Ch. Eigler
2008-11-06 22:25                         ` Mathieu Desnoyers
2008-11-06 23:25                           ` Frank Ch. Eigler
2008-11-07  4:25                             ` Arjan van de Ven
2008-11-07  5:12                             ` Mathieu Desnoyers
2008-11-06 21:13                   ` Arjan van de Ven
2008-11-06 21:20                     ` Frank Ch. Eigler
2008-11-06 14:14   ` Arjan van de Ven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081105194326.GA5839@joi \
    --to=marcin.slusarz@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.