linux-kernel - how the mmap() work for scatter

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]

Date:	Sun, 21 Mar 2010 09:32:04 +0800
From:	"Figo.zhang" <figo1802@...il.com>
To:	lkml <linux-kernel@...r.kernel.org>
Subject: how the mmap() work for scatter_sg memory?

hi all,

i see the drm kernel source code, for SCATTER MEMORY, it use
vmalloc_32() to alloce some pages, and put them into sglist table in
drm_scatter.c. and in drm_mmap_locked(), why it not call
remap_vmalloc_range() to remap the pages to vm_area for mmap? how it
remap pages(that memory using vmalloc_32() to alloc) to vm_area? 
for consistany memory, it often call remap_pfn_range() for remap.
so i am puzzle how the mmap() is work for sg? would someone give it more
details? Thanks.

Best
Figo

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