linux-ext4 - Re: [PATCH] ext4/jbd2: remove stray markers

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

Message-ID: <20090506110354.GG25203@elte.hu>
Date:	Wed, 6 May 2009 13:03:54 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4/jbd2: remove stray markers


* Christoph Hellwig <hch@....de> wrote:

> ext4/jbd2 has a couple of stray markers without any users 
> introduced in commit ba80b1019aa722b24506db1ee755e0bb2f513022 
> (which has a very useless changelog, btw).  Remove them in 
> preparation of removing the markers in favour of the TRACE_EVENT 
> macro (and also because we don't keep dead code around).
> 
> Ted, I think you have some TRAVE_EVENT patches for ext4 pending, 
> but is it okay to queue up this removal in the tracing tree?  That 
> way we can remove the markers leftovers there completely as soon 
> as the 2.6.31 merge window opens.

i think these markers are still in active use, so i'd not remove 
them before Ted's TRACE_EVENT() changes are included. We can/should 
do that in a single topic - in a work flow that suits Ted best.

We can do a -git based special-purpose topic branch in -tip, or we 
can do it in tip/tracing, or we can pull a (-git based) branch from 
Ted. Or we can delay it all to the v2.6.31 merge window. Ted's 
choice.

	Ingo
--
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