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

Message-ID: <20090506131824.GB1325@elte.hu>
Date:	Wed, 6 May 2009 15:18:24 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Theodore Tso <tytso@....edu>, Christoph Hellwig <hch@....de>,
	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


* Theodore Tso <tytso@....edu> wrote:

> On Wed, May 06, 2009 at 01:44:15PM +0200, Christoph Hellwig wrote:
> > On Wed, May 06, 2009 at 07:40:51AM -0400, Theodore Tso wrote:
> > > My complaint with Cristoph's
> > 
> > Christoph, still :)
> 
> Sorry, I keep making that mistake!  Keep calling me on it, and
> eventually I'll reprogram those finger macros.  :-)
> 
> 
> > Also without Steve's updates you can't actually use them in a module.
> 
> Yep; not sure *how* critical that would be for -next, though. 
> Probably there would be some complaints....
> 
> In any case, it'll be less work to worry about patch conflicts if 
> we just do it during the merge window.  If we can just arrange to 
> push the tip/tracing changes early, I'll push the marker 
> replacement patches as soon as I see them hit mainline.

Cool, thanks! I'll try to aim for an early merge of the tracing 
tree. (And such dependent patches are generally possible shortly 
after -rc1 as well, especially if the clean-up factor is 
significant.)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/