Hi, I am looking at the latest mm/memory.c on Bitkeeper. The comment for remap_pte_range() says "maps a range of physical memory into the requested pages. the old mappings are removed". But the code has this check: BUG_ON(!pte_none(*pte)); Why is it a bug to have a valid PTE when remap_pte_range() is called? The 2.4 version of this fucntion cleared the old PTE using ptep_get_and_clear() and then installed a new one. Why was this changed? Thanks, Ravi. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
