Skip to contentSkip to conversation

truncate () doesn't clear partial pages

PATCH In review Miloslav Trmac 2 participants 3 messages Dec 10, 2000

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 truncate () doesn't clear partial pages

Hi,
vmtruncate () in test11 doesn't clear ends of partial pages. Patch is attached below.
HOWEVER, it doesn't fix everything: partial_clear () contains

        if (!pte_present(pte))
                return;

so swapped-out pages don't get truncated (so the patch seems to break things:
truncate () behaves differently under memory pressure).
To reproduce:
------tst.c:
int
main (int argc, char *argv[])
{
int fd;
volatile char *base, *p;
unsigned i, len;

fd = open (argv[1], O_RDWR);
len = atoi (argv[2]) * 1048576;
base = mmap (NULL, len, PROT_READ | PROT_WRITE, MAP_PRIVATE, fd, 0); p = base;
base[49] = 1;
base[50] = 2;
for (i = len / 4096; i != 0; i--)

    { /* Touch all pages to eat memory and force swapping the 1st page out */
      *p = 1;
      p += 4096;
    }

ftruncate (fd, 50);
printf ("%u,%u\n", base[49], base[50]);
return 0;
}
------

$ dd bs=1M count=$MEGS </dev/zero >tmp
$ ./tst tmp $MEGS
Plain test11 prints always 1,2 (i.e. partial page unaffected), patched
prints 1,0 if $MEGS is low enough, 1,2 if the first page was swapped out
($MEGS >= your RAM size).
The swap case should probably be handled as in ptrace.c: access_one_page()
(fault_in_page), but I don't understand the kernel well enough.
	Mirek Trmac
memory.c renamed from memory.c.orig +11 -8
@@ -935,7 +935,7 @@
 		unsigned long diff;
 
 		/* mapping wholly truncated? */
-		if (mpnt->vm_pgoff >= pgoff) {
+		if (mpnt->vm_pgoff > pgoff) {
 			flush_cache_range(mm, start, end);
 			zap_page_range(mm, start, len);
 			flush_tlb_range(mm, start, end);
@@ -951,13 +951,16 @@
 		/* Ok, partially affected.. */
 		start += diff << PAGE_SHIFT;
 		len = (len - diff) << PAGE_SHIFT;
-		if (start & ~PAGE_MASK) {
-			partial_clear(mpnt, start);
-			start = (start + ~PAGE_MASK) & PAGE_MASK;
+		if (partial) {
+			partial_clear(mpnt, start + partial);
+			start += PAGE_SIZE;
+			len -= PAGE_SIZE;
+		}
+		if (len) {
+			flush_cache_range(mm, start, end);
+			zap_page_range(mm, start, len);
+			flush_tlb_range(mm, start, end);
 		}
-		flush_cache_range(mm, start, end);
-		zap_page_range(mm, start, len);
-		flush_tlb_range(mm, start, end);
 	} while ((mpnt = mpnt->vm_next_share) != NULL);
 }
 			      
@@ -984,7 +987,7 @@
 	if (!mapping->i_mmap && !mapping->i_mmap_shared)
 		goto out_unlock;
 
-	pgoff = (offset + PAGE_CACHE_SIZE - 1) >> PAGE_CACHE_SHIFT;
+	pgoff = offset >> PAGE_CACHE_SHIFT;
 	partial = (unsigned long)offset & (PAGE_CACHE_SIZE - 1);
 
 	if (mapping->i_mmap != NULL)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#1 lore raw
Quoted 2 lines · Miloslav Trmac

Hi,
vmtruncate () in test11 doesn't clear ends of partial pages. Patch is attached

It doesn't and it shouldn't. That's done in ->truncate(). Check ext2_truncate() for example.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
In reply to Miloslav Trmac

Hi,

Quoted 6 lines · Alexander Viro
Quoted 2 lines · Miloslav Trmac

Hi,
vmtruncate () in test11 doesn't clear ends of partial pages. Patch is attached

It doesn't and it shouldn't. That's done in ->truncate(). Check ext2_truncate() for example.

ext2_truncate () (or block_truncate_page (), to be precise) clears end of page-cache page. partial_clear () in mm/memory.c is IMHO supposed to clear ends of anonymous pages (created from COW on MAP_PRIVATE mappings). I wasn't adding any new functionality, just correcting the old implementation (which would never trigger).

[Yes, currently it would clear the end of the page-cache page as many times as the page is accessible trough a pte. partial_clear () should probably clear *only* anonymous and swap pages.]

Actually, I'm not that sure that MAP_PRIVATE partial pages should be cleared; SuSv2 only says "the whole pages beyond the new end will be discarded" [ftruncate ()] and "It is unspecified whether modifications to the underlying object done after the MAP_PRIVATE mapping is established are visible through the MAP_PRIVATE mapping." [mmap ()].
So maybe not clearing the pages is The Right Thing - especially as it avoids the trouble with swapped-out pages. Remove partial_clear () completely, then.
Mirek Trmac
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/