linux-kernel - Re: kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140!

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: <20070302214111.GL10643@holomorphy.com>
Date:	Fri, 2 Mar 2007 13:41:11 -0800
From:	Bill Irwin <bill.irwin@...cle.com>
To:	"Alexander Y. Fomichev" <gluk@...4.ru>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	admin@...t.net.ru
Subject: Re: kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140!

On Fri, Mar 02, 2007 at 04:51:15PM +0300, Alexander Y. Fomichev wrote:
> I'm hit a bug on 2.6.21-rc1 at startup of mysql with 'large-pages' flag set.
> (at this point mysql trying to allocate pages from hugetlb pool by sysv 
> shm syscalls). Seems like it could be triggered by previous badness
> and probably hugetlb itself is not related. Anyway i couldn't reproduce
> it by now with 2.6.21-rc2 git commit 562aa1d4c6a874373f9a48ac184f662fbbb06a04.
> Very likely it has been fixed somwhere between 2.6.21-rc1 and -rc2,
> but i couldn't find something related by git log so any comments are welcome.

If you have a known-working kernel version, git-bisect might help you
track down where it was introduced. Given the messages prior to the
hugetlbpage.c BUG_ON I'd say that this is something else besides the
specific code listed by line number, though I wouldn't rule out hugetlb
having tripped over itself before the actual BUG.


-- wli
-
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/