From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arch: arm64: kernel: sprintf(), 'str' needs additional 1 byte for failure processing
Date: Tue, 28 May 2013 11:42:50 +0100 [thread overview]
Message-ID: <20130528104250.GE10474@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <51A2BE2C.2000004@asianux.com>
Hello,
On Mon, May 27, 2013 at 03:00:12AM +0100, Chen Gang wrote:
>
> When failure occurs at the last looping cycle (when 'i == 0'), it will
> print "bad PC value" instead of "(%08x) ", which needs additional 1
> byte.
>
> If not add 1 byte, the 'str' may be memory overflow.
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> arch/arm64/kernel/traps.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 61d7dd2..c2f68d2 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -100,7 +100,7 @@ static void dump_instr(const char *lvl, struct pt_regs *regs)
> {
> unsigned long addr = instruction_pointer(regs);
> mm_segment_t fs;
> - char str[sizeof("00000000 ") * 5 + 2 + 1], *p = str;
> + char str[sizeof("00000000 ") * 5 + 2 + 1 + 1], *p = str;
> int i;
Whilst this code is difficult to follow, I don't think it's incorrect.
The size of the str array is:
sizeof("00000000 ") = 8 ('0's) + 1 (space) + 1 (NUL) = 10 bytes
*5 = 50 bytes
+2 (for the two brackets when i == 0) = 52 bytes
+1 (this is for the "bad PC value") = 53 bytes
In the worst case (when the PC is bad) we print:
"%08x " x4 = (8 + 1 + 1) *4 = 40 bytes
"bad PC value" = 12 + 1 = 13 bytes
so again, 53 bytes.
... or have I missed a character somewhere?
Will
next prev parent reply other threads:[~2013-05-28 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 10:28 [PATCH] arch: arm64: kernel: sprintf(), 'str' needs additional 1 byte for failure processing Chen Gang
2013-05-27 1:42 ` Chen Gang
2013-05-27 2:00 ` [PATCH v2] " Chen Gang
2013-05-28 10:42 ` Will Deacon [this message]
2013-05-28 11:21 ` Chen Gang
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=20130528104250.GE10474@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).