From: Cyrille Pitchen <cyrille.pitchen@atmel.com>
To: Joe Perches <joe@perches.com>
Cc: <dwmw2@infradead.org>, <linux-mtd@lists.infradead.org>,
<nicolas.ferre@atmel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] jffs2: fix buffer dump debug output
Date: Tue, 21 Oct 2014 11:47:34 +0200 [thread overview]
Message-ID: <54462BB6.5020405@atmel.com> (raw)
In-Reply-To: <1413879465.12828.1.camel@perches.com>
Le 21/10/2014 10:17, Joe Perches a écrit :
> On Tue, 2014-10-21 at 10:05 +0200, Cyrille Pitchen wrote:
>> This patch fixes __jffs2_dbg_dump_buffer(): this function prints a message
>> claiming to dump len bytes. However, depending on the start offset, the former
>> code drops up to 31 (JFFS2_BUFDUMP_BYTES_PER_LINE - 1) bytes.
>>
>> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>> ---
>> fs/jffs2/debug.c | 21 ++++++++-------------
>> 1 file changed, 8 insertions(+), 13 deletions(-)
>>
>> diff --git a/fs/jffs2/debug.c b/fs/jffs2/debug.c
>> index 07bd5bc..1b515b2 100644
>> --- a/fs/jffs2/debug.c
>> +++ b/fs/jffs2/debug.c
>> @@ -736,30 +736,25 @@ void
>> __jffs2_dbg_dump_buffer(unsigned char *buf, int len, uint32_t offs)
>> {
>> int skip;
>> - int i;
>> + int i, pos;
>>
>> printk(JFFS2_DBG_MSG_PREFIX " dump from offset %#08x to offset %#08x (%x bytes).\n",
>> offs, offs + len, len);
>> - i = skip = offs % JFFS2_BUFDUMP_BYTES_PER_LINE;
>> + i = skip = offs & (JFFS2_BUFDUMP_BYTES_PER_LINE - 1);
>> offs = offs & ~(JFFS2_BUFDUMP_BYTES_PER_LINE - 1);
>>
>> - if (skip != 0)
>> - printk(JFFS2_DBG "%#08x: ", offs);
>> -
>> + printk(JFFS2_DBG "%#08x: ", offs);
>> while (skip--)
>> printk(" ");
>>
>> - while (i < len) {
>> - if ((i % JFFS2_BUFDUMP_BYTES_PER_LINE) == 0 && i != len -1) {
>> - if (i != 0)
>> - printk("\n");
>> + for (pos = 0; pos < len; ++pos, ++i) {
>> + if (i == JFFS2_BUFDUMP_BYTES_PER_LINE) {
>> offs += JFFS2_BUFDUMP_BYTES_PER_LINE;
>> - printk(JFFS2_DBG "%0#8x: ", offs);
>> + printk(JFFS2_DBG "\n%0#8x: ", offs);
>> + i = 0;
>
> print_hex_dump would be better
>
>
Hi Joe,
thanks for your comment. Indeed using print_hex_dump() would be a good idea
since it would avoid each driver to implement its own version of buffer dumps.
Reading the source code of print_hex_dump(), the output format would change a
little bit:
the output would no longer be aligned to JFFS2_BUFDUMP_BYTES_PER_LINE boundary
using leading spaces.
If it's ok to change the output format it's good for me as well.
next prev parent reply other threads:[~2014-10-21 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 8:04 [PATCH 0/2] *** jffs2: fix debug outputs *** Cyrille Pitchen
2014-10-21 8:04 ` [PATCH 1/2] jffs2: fix wrong offset in an error msg from __jff2_dbg_prewrite_paranoia_check Cyrille Pitchen
2014-10-21 8:05 ` [PATCH 2/2] jffs2: fix buffer dump debug output Cyrille Pitchen
2014-10-21 8:17 ` Joe Perches
2014-10-21 9:47 ` Cyrille Pitchen [this message]
2014-10-21 9:54 ` Artem Bityutskiy
2014-10-21 10:17 ` Cyrille Pitchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54462BB6.5020405@atmel.com \
--to=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@atmel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox