linux-kernel - alloc_page_vma: should be called from a module? (not exported in x86

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>] [day] [month] [year] [list]

Message-ID: <a2e38900711291506l216fe3a0lb5b173939770139a@mail.gmail.com>
Date:	Fri, 30 Nov 2007 00:06:42 +0100
From:	"Alejandro Homs Puron" <ahoms@...rs.sourceforge.net>
To:	linux-kernel@...r.kernel.org
Cc:	ahoms@...f.fr
Subject: alloc_page_vma: should be called from a module? (not exported in x86_64)

Hi,

We've developed a driver for an image acquisition card, which maps
kernel alloc'ed buffers into user space vma's. We use alloc_page +
remap_pfn_range in the driver mmap file_operation.

After looking at alloc_page_vma, I thought that it might be more
appropiate than alloc_page in this context. However, if CONFIG_NUMA=y
(x86_64), this function is not visible to modules.

Is this limitation intentional?

We alloc RAM in a page-by-page basis. Is vm_insert_page more
appropiate than remap_pfn_range?

Thanks a lot for your help.

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