public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	mingo@elte.hu, Frederic Weisbecker <fweisbec@gmail.com>,
	auke-jan.h.kok@intel.com
Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function
Date: Wed, 11 Nov 2009 10:33:55 +0800	[thread overview]
Message-ID: <4AFA2293.5080803@cn.fujitsu.com> (raw)
In-Reply-To: <20091025225342.007138f5@infradead.org>

> +/*
> + * Tracepoint for dirtying an inode:
> + */
> +TRACE_EVENT(dirty_inode,
> +
> +	TP_PROTO(struct inode *inode, struct task_struct *task),
> +
> +	TP_ARGS(inode, task),
> +
> +	TP_STRUCT__entry(
> +		__array( char,	comm,	TASK_COMM_LEN	)
> +		__field( pid_t,	pid			)
> +		__array( char,  dev,    16		)
> +		__array( char,  file,   32		)
> +	),
> +
> +	TP_fast_assign(
> +		if (inode->i_ino || strcmp(inode->i_sb->s_id, "bdev")) {
> +                	struct dentry *dentry;
> +                	const char *name = "?";
> +
> +			dentry = d_find_alias(inode);
> +			if (dentry) {
> +				spin_lock(&dentry->d_lock);
> +				name = (const char *) dentry->d_name.name;
> +			}
> +
> +			memcpy(__entry->comm, task->comm, TASK_COMM_LEN);
> +			__entry->pid = task->pid;
> +			strlcpy(__entry->file, name, 32);
> +			strlcpy(__entry->dev, inode->i_sb->s_id, 16);
> +
> +			if (dentry) {
> +				spin_unlock(&dentry->d_lock);
> +				dput(dentry);
> +			}
> +		}

This will leave __entry->comm, __entry->file and __entry->dev
uninitialized in the "else" case..

And is there any reason that we have to use __array() but can't
use __string()?

> +	),
> +
> +	TP_printk("task=%i (%s) file=%s dev=%s",
> +		__entry->pid, __entry->comm, __entry->file, __entry->dev)
> +);
> +
> +#endif /* _TRACE_VFS_H */

  parent reply	other threads:[~2009-11-11  2:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  5:53 [PATCH] vfs: Add a trace point in the mark_inode_dirty function Arjan van de Ven
2009-10-26  6:03 ` Andrew Morton
2009-10-26  6:55   ` Arjan van de Ven
2009-10-27 16:01 ` Jason Baron
2009-11-11  2:01 ` Wu Fengguang
2009-11-11  6:34   ` Arjan van de Ven
2009-11-11  6:40     ` Wu Fengguang
2009-11-11  7:42     ` Jeff Garzik
2009-11-11  7:45       ` Ingo Molnar
2009-11-11  7:56         ` Jeff Garzik
2009-11-11 11:15           ` Ingo Molnar
2009-11-11 17:27         ` Kok, Auke
2009-11-11 18:29         ` Theodore Tso
2009-11-11 18:56           ` Ingo Molnar
2009-11-12  2:15           ` Arjan van de Ven
2009-11-11 16:19       ` Arjan van de Ven
2009-11-11 23:10         ` Frank Ch. Eigler
2009-11-11 23:37           ` Kok, Auke
2009-11-12  7:22             ` Ingo Molnar
2009-11-20 10:43               ` Christoph Hellwig
2009-11-20 10:51                 ` Ingo Molnar
2009-11-20 14:45                 ` Arjan van de Ven
2009-11-20 16:05                   ` Jamie Lokier
2009-11-20 16:45                     ` Arjan van de Ven
2009-11-11  2:33 ` Li Zefan [this message]
2009-11-15 19:00   ` Arjan van de Ven
2009-11-16  0:56     ` Li Zefan

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=4AFA2293.5080803@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=arjan@infradead.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=viro@ZenIV.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox