linux-kernel - Re: [PATCH] blktrace: correct remap names

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: <4A0174E4.5090002@hp.com>
Date:	Wed, 06 May 2009 07:30:44 -0400
From:	"Alan D. Brunelle" <Alan.Brunelle@...com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Li Zefan <lizf@...fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <srostedt@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH] blktrace: correct remap names

Ingo Molnar wrote:
> * Li Zefan <lizf@...fujitsu.com> wrote:
> 
>>> Subject: [PATCH] blktrace: correct remap names
>>>
>>> This attempts to clarify names utilized during block I/O remap operations
>>> (partition, volume manager). It correctly matches up the /from/ information for both device & sector. This takes in the concept from osaki Motohiro and extends it to include better naming for the "device_from" field.
>>>
>> I also noticed this..
>>
>>> Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
>>> Cc: Li Zefan <lizf@...fujitsu.com>
>>> Cc: Jens Axboe <jens.axboe@...cle.com>
>>> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
>>> Signed-off-by: Alan D. Brunelle <alan.brunelle@...com>
>>> ---
>>>  include/linux/blktrace_api.h |    4 ++--
>>>  include/trace/block.h        |    4 ++--
>>>  kernel/trace/blktrace.c      |   21 +++++++++++----------
>>>  3 files changed, 15 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/include/linux/blktrace_api.h b/include/linux/blktrace_api.h
>>> index d960889..da1a14e 100644
>>> --- a/include/linux/blktrace_api.h
>>> +++ b/include/linux/blktrace_api.h
>>> @@ -116,9 +116,9 @@ struct blk_io_trace {
>>>   * The remap event
>>>   */
>>>  struct blk_io_trace_remap {
>>> -	__be32 device;
>>>  	__be32 device_from;
>>> -	__be64 sector;
>>> +	__be32 device_to;
>>> +	__be64 sector_from;
>>>  };
>>>  
>> If we are really fine with this change, then:
>>
>> Reviewed-by: Li Zefan <lizf@...fujitsu.com>
> 
> is it acceptable to break the sector output ordering of all past 
> blktrace+blkparse binaries, as far as remap events go?
> 
> 	Ingo

The binary order of data sent remains the same: the field names for the
structure & parameters passed around were wrong^Wmisleading (as was
pointed out previously by Kosaki Motoiro). I've tested this and the
blkparse output remains identical (both with the previous version of
blktrace/blkparse & with a posted patch to blkparse which also fixes the
field names of blk_io_trace_remap). The testing included permutations of
(old/new) kernel traces & (old/new) blkparse. They all resulted in the
same blkparse output.

Alan
--
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/