From: Joe Perches <joe@perches.com>
To: "Horacio Mijail Antón Quiles" <hmijail@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
David Howells <dhowells@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [RESEND 2][PATCH v4] hexdump: fix for non-aligned buffers
Date: Wed, 08 Jul 2015 16:49:02 -0700 [thread overview]
Message-ID: <1436399342.2682.94.camel@perches.com> (raw)
In-Reply-To: <20150708234418.GA9541@mija-VirtualBox>
On Thu, 2015-07-09 at 01:44 +0200, Horacio Mijail Antón Quiles wrote:
> An hexdump with a buf not aligned to the groupsize causes
> non-naturally-aligned memory accesses. This was causing a kernel panic on
> the processor BlackFin BF527, when such an unaligned buffer was fed by the
> function ubifs_scanned_corruption in fs/ubifs/scan.c .
Seems sensible enough to me.
> ---
> diff --git a/lib/hexdump.c b/lib/hexdump.c
[]
> @@ -124,6 +124,11 @@ int hex_dump_to_buffer(const void *buf, size_t len, int rowsize, int groupsize,
> if ((len % groupsize) != 0) /* no mixed size output */
> groupsize = 1;
>
> + /* fall back to 1-byte groups if buf is not aligned to groupsize */
> + if (!IS_ENABLED(CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS) &&
> + !IS_ALIGNED((uintptr_t)buf, groupsize))
> + groupsize = 1;
> +
> ngroups = len / groupsize;
> ascii_column = rowsize * 2 + rowsize / groupsize + 1;
>
next prev parent reply other threads:[~2015-07-08 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 23:44 [RESEND 2][PATCH v4] hexdump: fix for non-aligned buffers Horacio Mijail Antón Quiles
2015-07-08 23:49 ` Joe Perches [this message]
2015-07-09 0:03 ` Andrew Morton
2015-07-09 1:36 ` H. Mijail
2015-07-09 2:07 ` Andrew Morton
2015-07-09 7:16 ` Geert Uytterhoeven
2015-07-09 19:08 ` H. Mijail
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=1436399342.2682.94.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=hmijail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.