1. 03 8月, 2008 3 次提交
    • L
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6 · d9c56619
      Linus Torvalds 提交于
      * git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6:
        sparc64: Do not clobber %g7 in setcontext() trap.
        sparc64: Kill __show_regs().
        sparc: Add __KERNEL__ ifdef protection to pt_regs helpers.
        sparc64: Kill smp_report_regs().
        sparc64: Kill VERBOSE_SHOWREGS code.
        sparc64: Hook up trigger_all_cpu_backtrace().
        sparc64: Make global reg dumping even more useful.
        sparc: Ignore drivers/video/console/promcon_tbl.c conmakehash generated file
        sparc64: FUTEX_OP_ANDN fix
        sparc: merge of_platform_{32,64}.h
        sparc64: Kill isa_bus_type.
        sparc64: Fix global reg snapshotting on self-cpu.
      d9c56619
    • O
      fat: Fix allow_utime option · 17263849
      OGAWA Hirofumi 提交于
      FAT has to handle the newly introduced ATTR_TIMES_SET for allow_utime
      option.
      Signed-off-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      17263849
    • M
      mm: dont clear PG_uptodate on truncate/invalidate · 84209e02
      Miklos Szeredi 提交于
      Brian Wang reported that a FUSE filesystem exported through NFS could
      return I/O errors on read.  This was traced to splice_direct_to_actor()
      returning a short or zero count when racing with page invalidation.
      
      However this is not FUSE or NFSD specific, other filesystems (notably
      NFS) also call invalidate_inode_pages2() to purge stale data from the
      cache.
      
      If this happens while such pages are sitting in a pipe buffer, then
      splice(2) from the pipe can return zero, and read(2) from the pipe can
      return ENODATA.
      
      The zero return is especially bad, since it implies end-of-file or
      disconnected pipe/socket, and is documented as such for splice.  But
      returning an error for read() is also nasty, when in fact there was no
      error (data becoming stale is not an error).
      
      The same problems can be triggered by "hole punching" with
      madvise(MADV_REMOVE).
      
      Fix this by not clearing the PG_uptodate flag on truncation and
      invalidation.
      Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      Acked-by: NNick Piggin <nickpiggin@yahoo.com.au>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Jens Axboe <jens.axboe@oracle.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      84209e02
  2. 02 8月, 2008 37 次提交