All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
	"Christoph Egger" <siccegge@cs.fau.de>,
	linux-kernel@vger.kernel.org,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	"Michal Marek" <mmarek@suse.cz>
Subject: Re: Bus error on make allyesconfig, kernelbuild with HEAD
Date: Sat, 6 Nov 2010 17:24:26 +0100	[thread overview]
Message-ID: <20101106162426.GA14361@merkur.ravnborg.org> (raw)
In-Reply-To: <87aalmcv0p.fsf@gmail.com>

On Sat, Nov 06, 2010 at 11:49:10AM -0400, Ben Gamari wrote:
> On Sat, 06 Nov 2010 11:07:48 -0400, Ben Gamari <bgamari.foss@gmail.com> wrote:
> > On Fri, 30 Jul 2010 16:43:53 +0800, Américo Wang <xiyou.wangcong@gmail.com> wrote:
> > > This is useful. :) Looks like parse_dep_file() accesses out of
> > > the mmap'ed memory range...
> > > 
> > Did anything ever happen with this? I seem to be experiencing similar
> > issues while cross-compiling for ARM on x86-64. All tested kernels
> > (v2.6.35 to master) fail with,

Too k a quick look.
Does the following patch fix it?

if m == p then we will stay in the while look looking for a space.
I did not audit all of the code - there may be other issues..

	Sam

diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
index ea26b23..f472ada 100644
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -318,7 +318,7 @@ static void parse_dep_file(void *map, size_t len)
 		while (m < end && (*m == ' ' || *m == '\\' || *m == '\n'))
 			m++;
 		p = m;
-		while (p < end && *p != ' ') p++;
+		while (p <= end && *p != ' ') p++;
 		if (p == end) {
 			do p--; while (!isalnum(*p));
 			p++;


  reply	other threads:[~2010-11-06 16:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 10:52 Bus error on make allyesconfig, kernelbuild with HEAD Christoph Egger
2010-07-29 11:26 ` Américo Wang
2010-07-29 11:57   ` Christoph Egger
2010-07-29 12:10   ` Christoph Egger
2010-07-30  8:43     ` Américo Wang
2010-11-06 15:07       ` Ben Gamari
2010-11-06 15:49         ` Ben Gamari
2010-11-06 16:24           ` Sam Ravnborg [this message]
2010-11-07 16:39             ` Ben Gamari
2010-11-07 16:44             ` Ben Gamari
2010-11-07 16:48               ` [PATCH] Debug fixdep Ben Gamari
2010-11-07 17:07               ` Bus error on make allyesconfig, kernelbuild with HEAD Sam Ravnborg
2010-11-07 18:09                 ` Ben Gamari
2010-11-07 22:30                   ` fstat suddenly return -EINVAL [Was: Bus error on make allyesconfig, kernelbuild with HEAD] Sam Ravnborg
2010-11-07 23:07                     ` Ben Gamari
2010-11-08 10:20                       ` Américo Wang
2010-11-08 12:38                         ` Ben Gamari
2010-11-08 12:38                           ` Ben Gamari
2010-11-08 18:22                           ` Sam Ravnborg
2010-11-08 18:22                             ` Sam Ravnborg
2010-11-08 18:42                             ` Ben Gamari
2010-11-08 19:05                               ` Sam Ravnborg
2010-11-08 20:17                                 ` Ben Gamari
2010-11-09 10:29                                   ` Américo Wang

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=20101106162426.GA14361@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bgamari.foss@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=siccegge@cs.fau.de \
    --cc=xiyou.wangcong@gmail.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.