linux-kernel - Re: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]

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: <200902092154.46695.nickpiggin@yahoo.com.au>
Date:	Mon, 9 Feb 2009 21:54:45 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	wixor <wixorpeek@...il.com>
Cc:	Alexey Dobriyan <adobriyan@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	JosephChan@....com.tw, linux-kernel@...r.kernel.org
Subject: Re: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]

On Monday 09 February 2009 21:06:32 wixor wrote:
> Yes, that is somehow better. BUG is gone, it says now
>    vmap allocation failed: use vmalloc=<size> to increase size
> and then
>    ioremap failed.
> The driver still doesn't work however.

Quite possibly then it is a bad size being passed to ioremap.
(as you said you still have a few hundred GB of vmalloc space
free).

Could you printk the value of the 'size' variable, and also
call WARN() in the case of allocation failure?

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