linux-kernel - Removing VM_LOCKED from user memory

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: <200704251429.26014.eike-kernel@sf-tec.de>
Date:	Wed, 25 Apr 2007 14:29:17 +0200
From:	Rolf Eike Beer <eike-kernel@...tec.de>
To:	linux-mm@...ck.org
Cc:	linux-kernel@...r.kernel.org
Subject: Removing VM_LOCKED from user memory

Hi,

I need some assistance handling a large memory segment of a user process.

The user calls the kernel with a address and a length of it's own memory. My 
driver will lock this memory using get_user_pages(). This memory is used as 
DMA buffer directly from or to user processes.

Everything works fine that far: allocating, DMA mapping, DMA transfers. But I 
currently can't get rid of the buffer again. Which function would help me to 
get all pages unlocked once the buffer isn't needed anymore?

Is it enough to simply call sys_munlock() from the release and cleanup 
functions?

There are no plans to share these mappings between different processes.

Greetings,

Eike

Download attachment "signature.asc " of type "application/pgp-signature" (190 bytes)