Messages in this thread | | | Date | Fri, 4 Apr 2003 08:14:57 -0800 | From | William Lee Irwin III <> | Subject | Re: objrmap and vmtruncate |
| |
On Fri, Apr 04, 2003 at 03:34:48PM +0100, Hugh Dickins wrote: > I see you're going for locking the page around page_convert_anon, > to guard page->mapping against truncation. Nice thought, > but the words "tip" and "iceberg" spring to mind. > Truncating a sys_remap_file_pages file? You're the first to > begin to consider such an absurd possibility: vmtruncate_list > still believes vm_pgoff tells it what needs to be done. > I propose that we don't change vmtruncate_list, zap_page_range, ... > at all for this: let it unmap inappropriate pages, even from a > VM_LOCKED vma, that's just a price userspace pays for the > privilege of truncating a sys_remap_file_pages file.
Hmm, aren't the file offset calculations wrong for sys_remap_file_pages() even before objrmap?
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |