Windows map DLL 是否指向不同进程中的相同虚拟地址？

Question

Say two processes are using Kernel32.dll, does Windows map the DLLs to the same virtual address space in both processes? If not, how does paging mechanism end up using the same physical address where the DLL is in fact loaded for both processes? I tried finding this info in the windows internals book but didn't find anything

Answer 1

TL;DR: No, it might be loaded somewhere else in another process.

Ntdll and Kernel32 are special and always load at the same address so it is better to focus on something else, Shell32 for example.

A dll has what is known as a preferred base address and this is stored in the PE header ( ImageBase ). The loader will first attempt to load the dll at this address. If that address range is free then loading will succeed with no extra work required.

If the address is not free then the loader has to load it somewhere else. Loading at a different address usually requires relocation information and if this was removed during linking ( /FIXED ) then loading will fail, If there was space somewhere else to load the dll. the loader will use the relocation information to patch the given locations in the dll with the new base address, Because dlls are loaded as copy-on-write. this will cause extra memory usage compared to loading at the preferred address since each memory page that needed a patch is now a private copy in the process, This means that the answer to your question is no. a dll might not load at the same address in a different process if that process already has something else loaded there.

So far I have only talked about the loader. The loader is implemented in Ntdll as normal usermode code and is not involved with how a file mapped into memory actually works. Memory mapped files (known as Sections internally in NT) is a co-operation between the operating system kernel and the CPU hardware. This is a whole topic in of itself but the important thing to know is that physical memory and the page/swap file mechanism is completely disconnected from how a usermode process accesses its virtual memory pages. The kernel can map a physical memory page to zero, one, or multiple places in a processes virtual memory and the CPU will automatically translate when a virtual page is accessed by the process.

As a final note, ASLR does complicate things a little bit but the "offset" only changes on reboot and should not have an impact on this specific question in current implementations. In theory Windows could change this in the future and always load things at different addresses in different processes but this is unlikely to happen because of the copy-on-write downsides.