linux-ext4 - Re: [PATCH 3/3] ext4: add tracepoint in punching hole

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

Date:	Fri, 18 Jan 2013 10:28:08 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Lukas Czerner <lczerner@...hat.com>,
	Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [PATCH 3/3] ext4: add tracepoint in punching hole

On Wed, Jan 16, 2013 at 10:38:22PM -0500, Theodore Ts'o wrote:
> On Thu, Aug 23, 2012 at 12:25:41PM +0800, Zheng Liu wrote:
> > From: Zheng Liu <wenqing.lz@...bao.com>
> > 
> > This patch adds a tracepoint in ext4_punch_hole.
> > 
> > CC: Lukas Czerner <lczerner@...hat.com>
> > Signed-off-by: Zheng Liu <wenqing.lz@...bao.com>
> 
> I'm still waiting for the next version of the indirect punch patches
> (which you said you'd work on after the extent status patches, given
> that I had noted other xfstest failures that were apparently caused by
> these patches), but in the mean time, adding a tracepoint for
> ext4_punch_hole() seem like it would make sense, so I've applied this
> patch to the ext4 tree.

Oops, my apology.  I forgot to CC' patches [1] to you.  It is my fault.
This patch should be fine because there is no any changes.  I will
rebase the others against 3.8-rc3, and run xfstest to make sure that it
is OK.  Later I will resend them to the mailling list.

1. http://comments.gmane.org/gmane.comp.file-systems.ext4/35491

Thanks,
                                                - Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html