linux-kernel - Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200808142229.28624.rjw@sisk.pl>
Date:	Thu, 14 Aug 2008 22:29:28 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Alan D. Brunelle" <Alan.Brunelle@...com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Linux 2.6.27-rc3: kernel BUG at mm/vmalloc.c - bisected

On Thursday, 14 of August 2008, Alan D. Brunelle wrote:
> Rafael J. Wysocki wrote:
> > On Thursday, 14 of August 2008, Alan D. Brunelle wrote:
> >> I ran into this trying 2.6.27-rc3 today:
> >>
> >> [6.461876] kernel BUG at mm/vmalloc.c:217!
> >>
> >> (full boot log attached)
> >>
> >> I bisected it to:
> >>
> >> git-bisect bad 1c89ac55017f982355c7761e1c912c88c941483d
> >>
> >> which is:
> >>
> >> commit 1c89ac55017f982355c7761e1c912c88c941483d
> >> Merge: 88fa08f... b1b135c...
> >> Author: Linus Torvalds <torvalds@...ux-foundation.org>
> >> Date:   Tue Aug 12 08:40:19 2008 -0700
> >>
> >>     Merge
> >> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus
> > 
> > This is a merge commit that introduced several changes into the
> > kernel.  It would be helpful to search through these changes.
> 
> I came in this morning, and did a 'git bisect reset' and 'git pull'
> built, and everything booted fine. I don't know if some fix came in for
> something else, or if the problem got "hidden" (some sort of timing
> thing, so the problem still lurks). If you feel it's important to track
> this down, if you could give me instructions on how to break apart that
> one merge, I could then try individual kernels from there...

I have created a Bugzilla entry at
http://bugzilla.kernel.org/show_bug.cgi?id=11342
for this problem.  I'll close it now, but please reopen if if the problem
reappears.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/