On Mon, 21 Mar 2005, David S. Miller wrote: > > flush_tlb_pgtables() on sparc64 has a BUG() check which > is basically: > > BUG((long)start > (long)end); > > This catches two cases of bogus arguments: > > 1) start --> end straddles sparc64 address space hole
That's an interesting remark. I hadn't noticed the signed long type. I believe the vma gathering in free_pgtables will have no problem with that, but what about the old code? What happens if an app does a huge munmap straddling the address space hole? Or is all the user address space below the hole? Hugh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/