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]
Date:	Tue, 16 Jan 2007 00:21:33 -0500
From:	David Moore <dcm@....EDU>
To:	Kristian Høgsberg <krh@...planet.net>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux1394-devel@...ts.sourceforge.net,
	theSeinfeld@...rs.sourceforge.net,
	Bill Davidsen <davidsen@....com>, linux-kernel@...r.kernel.org,
	libdc1394-devel@...ts.sourceforge.net
Subject: Re: allocation failed: out of vmalloc space error treating and
	VIDEO1394 IOC LISTEN CHANNEL ioctl failed problem

On Mon, 2007-01-15 at 16:43 -0500, Kristian Høgsberg wrote:
> On 1/15/07, Arjan van de Ven <arjan@...radead.org> wrote:
> > again the best way is for you to provide an mmap method... you can then
> > fill in the pages and keep that in some sort of array; this is for
> > example also what the DRI/DRM layer does for textures etc...
> 
> That sounds a lot like what I have now (mmap method, array of pages)
> so I'll just stick with that.

It sounds like the distinction Arjan is getting at is that the buffer
should exist in the process's virtual address space instead of the
kernel's virtual address space so that we have plenty of space available
to us.

Thus, we should use get_user_pages() instead of vmalloc().  I think
get_user_pages() will also automatically pin the memory.  And we'll also
need to call get_user_pages() from a custom mmap() handler so that we
know what process virtual address to assign to the region.

Is that right Arjan?

Thanks,

David

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

Powered by blists - more mailing lists