From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function
Date: Sun, 15 Nov 2009 11:00:43 -0800
Message-ID: <20091115110043.6cafc221@infradead.org>
References: <20091025225342.007138f5@infradead.org>
	<4AFA2293.5080803@cn.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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
To: Li Zefan <lizf@cn.fujitsu.com>
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1753454AbZKOS7J@vger.kernel.org>
In-Reply-To: <4AFA2293.5080803@cn.fujitsu.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Wed, 11 Nov 2009 10:33:55 +0800
Li Zefan <lizf@cn.fujitsu.com> wrote:
> 
> This will leave __entry->comm, __entry->file and __entry->dev
> uninitialized in the "else" case..

I would expect the struct to be zeroed before.... is it?
(the TP_ stuff is so obscure I find it hard to figure out where it ends
up)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org