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

[Li Zefan <lizf@cn.fujitsu.com>]

Ingo Molnar wrote:
> * Li Zefan <lizf@cn.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?
> 

It should be find to merge tip/blktrace into .30, and we still have 2
month to fix remaining bugs, if any.

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