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]

Date:	Wed, 6 May 2009 13:58:50 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@....de>
Cc:	Theodore Tso <tytso@....edu>, linux-kernel@...r.kernel.org,
	Fr?d?ric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4/jbd2: remove stray markers


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

> I was planning to do make sure it's all gone.  Once we are into 
> the 2.6.31 merge dinwo I fear that the final patches will miss the 
> window due to all these interdependencies.  But Ingo didn't seem 
> to be too interested in taking the other patches that would be 
> required for it, so I guess I'll try to somehow get it done in the 
> merge window and otherwise we'll have to wait for 2.6.32.

Well, while coupling to lots of subsystems is natural for something 
as intrinsic as the tracing tree - still i dont want to over-do it. 
In little over a month these patches can go into their local 
subsystem trees, without any interactions with anything.

So the patches you did are nice - just (as it is usual with any core 
kernel tree) the logistics have to be planned carefully.

	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