From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Adrian Bunk <bunk@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: m68k: main.c:(.init.text+0x730): undefined reference to `strlen'
Date: Wed, 14 May 2008 19:14:07 +0400 [thread overview]
Message-ID: <20080514151407.GD6902@cvg> (raw)
In-Reply-To: <je63thszo6.fsf@sykes.suse.de>
[Andreas Schwab - Wed, May 14, 2008 at 04:55:37PM +0200]
| Cyrill Gorcunov <gorcunov@gmail.com> writes:
|
| > I think it would help to see ..tmp_vmlinux1.cmd to ensure for inclusion
| > of lib/lib.a. strlen was there without my patch as Andreas already pointed,
| > I've just added strncat wich is coming from lib/string.o for this arch.
|
| Actually the way strncat is used here is broken anyway, it does not
| prevent array overrun. The third argument of strncat only limits the
| amount of characters copied, without taking into account the length of
| the string already in the buffer. Consequently gcc has optimized the
| call to strncat into a simple call to strcat, since none of the copied
| strings are longer than sizeof(msgbuf). This strcat call is then
| expanded to include a call to strlen.
|
| So a better fix would probably be to make msgbuf big enough and use
| strcat instead.
|
| Andreas.
|
|
Andreas, could you test/review the following patch
(what is worse - I *have* introduced buffer overflow with my
patch, so I think we should fix it asap)
---
Index: linux-2.6.git/init/main.c
===================================================================
--- linux-2.6.git.orig/init/main.c 2008-05-14 17:55:10.000000000 +0400
+++ linux-2.6.git/init/main.c 2008-05-14 19:11:18.000000000 +0400
@@ -702,7 +702,7 @@ static void __init do_initcalls(void)
for (call = __initcall_start; call < __initcall_end; call++) {
ktime_t t0, t1, delta;
- char msgbuf[40];
+ char msgbuf[64];
int result;
if (initcall_debug) {
@@ -729,11 +729,11 @@ static void __init do_initcalls(void)
sprintf(msgbuf, "error code %d ", result);
if (preempt_count() != count) {
- strncat(msgbuf, "preemption imbalance ", sizeof(msgbuf));
+ strcat(msgbuf, "preemption imbalance ");
preempt_count() = count;
}
if (irqs_disabled()) {
- strncat(msgbuf, "disabled interrupts ", sizeof(msgbuf));
+ strcat(msgbuf, "disabled interrupts ");
local_irq_enable();
}
if (msgbuf[0]) {
next prev parent reply other threads:[~2008-05-14 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 8:02 m68k: main.c:(.init.text+0x730): undefined reference to `strlen' Geert Uytterhoeven
2008-05-14 8:37 ` Andreas Schwab
2008-05-14 9:57 ` Cyrill Gorcunov
2008-05-14 10:48 ` Cyrill Gorcunov
2008-05-14 14:10 ` Adrian Bunk
2008-05-14 14:28 ` Andreas Schwab
2008-05-14 14:40 ` Cyrill Gorcunov
2008-05-14 14:55 ` Andreas Schwab
2008-05-14 14:58 ` Cyrill Gorcunov
2008-05-14 15:14 ` Cyrill Gorcunov [this message]
2008-05-14 15:27 ` Andreas Schwab
2008-05-14 15:31 ` Cyrill Gorcunov
2008-05-14 20:14 ` Geert Uytterhoeven
2008-05-14 14:51 ` Cyrill Gorcunov
2008-05-14 15:30 ` Adrian Bunk
2008-05-14 15:48 ` Cyrill Gorcunov
2008-05-14 15:56 ` Adrian Bunk
2008-05-14 16:03 ` Cyrill Gorcunov
2008-05-14 14:55 ` Roman Zippel
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=20080514151407.GD6902@cvg \
--to=gorcunov@gmail.com \
--cc=bunk@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@suse.de \
/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