linux-kernel - Re: [PATCH v2 0/7] blktrace: last round of fixes

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: <20090330011725.GB11087@elte.hu>
Date:	Mon, 30 Mar 2009 03:17:25 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Li Zefan <lizf@...fujitsu.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/7] blktrace: last round of fixes


* Jens Axboe <jens.axboe@...cle.com> wrote:

> On Sat, Mar 28 2009, Ingo Molnar wrote:
> > 
> > * Li Zefan <lizf@...fujitsu.com> wrote:
> > 
> > > This is the last round of fixes for blktrace, I hope.  :) 
> > > 
> > > Changelog v1 -> v2:
> > >   - fix a bug in "blktrace: make classic output more classic",
> > >     and rebase other patches.
> > >   - re-order patches.
> > >   - a new patch for filtering BLK_TN_MESSAGE
> > > 
> > > [PATCH v2 1/6] trace: make 'mem' argument of trace_seq_putmem() const
> > > [PATCH v2 2/6] blktrace: make classic output more classic
> > > [PATCH v2 3/6] blktrace: fix blk_probes_ref chaos
> > > [PATCH v2 4/6] blktrace: fix memory leak when freeing struct blk_io_trace
> > > [PATCH v2 5/6] blktrace: extract duplidate code
> > > [PATCH v2 6/6] blktrace: print out BLK_TN_MESSAGE properly
> > > ---
> > >  blktrace.c     |  188 +++++++++++++++++++++++++++++++++------------------------
> > >  trace_output.c |    6 -
> > >  trace_output.h |    5 -
> > >  3 files changed, 117 insertions(+), 82 deletions(-)
> > 
> > Li, Jens - what's your call for v2.6.30, can the blktrace changes go 
> > upstream or should i zap the whole thing?
> > 
> > There are no new -tip test failures here so it's green as far as i'm 
> > concerned. It's holding up the tracing tree so we need to decide one 
> > way or another.
> 
> If Li deems it ready, then it has my blessing as well.

thanks Jens - i have added your Acked-by's as well.

	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/