1. 12 9月, 2007 1 次提交
  2. 20 7月, 2007 1 次提交
    • N
      mm: merge populate and nopage into fault (fixes nonlinear) · 54cb8821
      Nick Piggin 提交于
      Nonlinear mappings are (AFAIKS) simply a virtual memory concept that encodes
      the virtual address -> file offset differently from linear mappings.
      
      ->populate is a layering violation because the filesystem/pagecache code
      should need to know anything about the virtual memory mapping.  The hitch here
      is that the ->nopage handler didn't pass down enough information (ie.  pgoff).
       But it is more logical to pass pgoff rather than have the ->nopage function
      calculate it itself anyway (because that's a similar layering violation).
      
      Having the populate handler install the pte itself is likewise a nasty thing
      to be doing.
      
      This patch introduces a new fault handler that replaces ->nopage and
      ->populate and (later) ->nopfn.  Most of the old mechanism is still in place
      so there is a lot of duplication and nice cleanups that can be removed if
      everyone switches over.
      
      The rationale for doing this in the first place is that nonlinear mappings are
      subject to the pagefault vs invalidate/truncate race too, and it seemed stupid
      to duplicate the synchronisation logic rather than just consolidate the two.
      
      After this patch, MAP_NONBLOCK no longer sets up ptes for pages present in
      pagecache.  Seems like a fringe functionality anyway.
      
      NOPAGE_REFAULT is removed.  This should be implemented with ->fault, and no
      users have hit mainline yet.
      
      [akpm@linux-foundation.org: cleanup]
      [randy.dunlap@oracle.com: doc. fixes for readahead]
      [akpm@linux-foundation.org: build fix]
      Signed-off-by: NNick Piggin <npiggin@suse.de>
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Mark Fasheh <mark.fasheh@oracle.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      54cb8821
  3. 11 7月, 2007 9 次提交
  4. 07 6月, 2007 1 次提交
    • M
      ocfs2: Fix invalid assertion during write on 64k pages · eeb47d12
      Mark Fasheh 提交于
      The write path code intends to bug if a math error (or unhandled case)
      results in a write outside of the current cluster boundaries. The actual
      BUG_ON() statements however are incorrect, leading to a crash on kernels
      with 64k page size. Fix those by checking against the right variables.
      
      Also, move the assertions higher up within the functions so that they trip
      *before* the code starts to mark buffers.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      eeb47d12
  5. 26 5月, 2007 2 次提交
  6. 03 5月, 2007 3 次提交
  7. 27 4月, 2007 10 次提交
  8. 15 3月, 2007 1 次提交
  9. 29 12月, 2006 1 次提交
    • M
      ocfs2: Allow direct I/O read past end of file · 564f8a32
      Mark Fasheh 提交于
      ocfs2_direct_IO_get_blocks() was incorrectly returning -EIO for a direct I/O
      read whose start block was past the end of the file allocation tree. Fix
      things so that we return a hole instead. do_direct_IO() will then notice
      that the range start is past eof and return a short read.
      
      While there, remove the unused vbo_max variable.
      Signed-off-by: NMark Fasheh <mark.fasheh@oracle.com>
      564f8a32
  10. 09 12月, 2006 1 次提交
  11. 02 12月, 2006 4 次提交
  12. 21 9月, 2006 1 次提交
  13. 30 6月, 2006 1 次提交
  14. 29 6月, 2006 1 次提交
  15. 18 5月, 2006 1 次提交
  16. 27 3月, 2006 1 次提交
  17. 25 3月, 2006 1 次提交