xfs-masters
[Top] [All Lists]

[xfs-masters] [Bug 418] New: unwritten extents remain unwritten after m

To: xfs-master@xxxxxxxxxxx
Subject: [xfs-masters] [Bug 418] New: unwritten extents remain unwritten after mmap() modifies them
From: bugzilla-daemon@xxxxxxxxxxx
Date: Thu, 28 Jul 2005 15:42:40 -0700
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=418

           Summary: unwritten extents remain unwritten after mmap() modifies
                    them
           Product: Linux XFS
           Version: Current
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XFS kernel code
        AssignedTo: xfs-master@xxxxxxxxxxx
        ReportedBy: wsl-xfs-bugzilla@xxxxxxxx


If a file is allocated using XFS_IOC_RESVSP64 then mmap()ed with PROT_WRITE and
written to (by altering bytes in the mmap()ed memory region), the extents remain
marked as ?unwritten? even after the file is munmap()ed.
If the data is still cached it will appear to the application that all is well,
but as soon as data is actually read from disk the ?unwritten? flag will cause
reads to be all zero again.

Note that the file had to be truncated upwards to the same size as the resvsp to
prevent a bus error when writing to the mmap()ed region.

-- 
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


<Prev in Thread] Current Thread [Next in Thread>
  • [xfs-masters] [Bug 418] New: unwritten extents remain unwritten after mmap() modifies them, bugzilla-daemon <=