xfs
[Top] [All Lists]

[XFS updates] XFS development tree branch, master, updated. v2.6.30-rc4-

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, master, updated. v2.6.30-rc4-24750-g44a743f
From: xfs@xxxxxxxxxxx
Date: Fri, 11 Dec 2009 15:21:15 -0600
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, master has been updated
  discards  9cdfb22ba2052d79461406aaa7a9e93a66018892 (commit)
  discards  291f6b4397b8c67742d1c94edd71e754e3d43a90 (commit)
  discards  64d27342a54d41a10ec66c377e6c380bbc4e5f2c (commit)
  discards  f08a7a4d08f9ce70d6157a9593495a0d6c7d21a2 (commit)
  discards  795659b57c2d4bb820f232afeeffb968470ea49a (commit)
  discards  ee4135cde4eae17e12575434228c20b6251b3246 (commit)
  discards  938ea15783552577b963a24912cc32f8ca19a8ef (commit)
  discards  5a3add466951ff3a0e728914955fadba8fa2eb73 (commit)
  discards  c684103b417672778324a79d85e23e45bbc3839b (commit)
  discards  c9b11d1381002e6fefcaf1d72d9ca4ddf866f471 (commit)
  discards  9b676b28aa618d02b7186169546c2af22e682e46 (commit)
  discards  63c8573fe7164cd4caac8197c04a2c27bb819f68 (commit)
  discards  66c0e0055f96a478428e25d0399aa14481a61ff4 (commit)
  discards  1698a43eab1ebb746c0190f21b91603bb5201880 (commit)
  discards  15bff0616833ae9f11873bf5fd0eb7524beee82c (commit)
  44a743f xfs: Fix error return for fallocate() on XFS
  30ac068 xfs: cleanup dmapi macros in the umount path
  0c3dc2b xfs: remove incorrect sparse annotation for xfs_iget_cache_miss
  b8f82a4 xfs: kill the STATIC_INLINE macro
  5683f53 xfs: uninline xfs_get_extsz_hint
  e82fa0c xfs: rename xfs_attr_fetch to xfs_attr_get_int
  6ad112b xfs: simplify xfs_buf_get / xfs_buf_read interfaces
  c355c65 xfs: remove IO_ISAIO
  fc5bc4c xfs: Wrapped journal record corruption on read at recovery
  5ec4fab xfs: cleanup data end I/O handlers
  06342cf xfs: use WRITE_SYNC_PLUG for synchronous writeout
  033da48 xfs: reset the i_iolock lock class in the reclaim path
  80641dc xfs: I/O completion handlers must use NOFS allocations
  c56c963 xfs: fix mmap_sem/iolock inversion in xfs_free_eofblocks
  848ce8f xfs: simplify inode teardown
      from  87a59023592e1bfe5f182dc605e4ee44fcdd60c6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 44a743f68705c681439f264deb05f8f38e9048d3
Author: Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx>
Date:   Tue Nov 24 21:52:53 2009 +0000

    xfs: Fix error return for fallocate() on XFS
    
    Noticed that through glibc fallocate would return 28 rather than -1
    and errno = 28 for ENOSPC. The xfs routines uses XFS_ERROR format
    positive return error codes while the syscalls use negative return
    codes.  Fixup the two cases in xfs_vn_fallocate syscall to convert to
    negative.
    
    Signed-off-by: Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx>
    Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 30ac0683dd452ba273c8db92a74d8cf7aef981d8
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:24 2009 +0000

    xfs: cleanup dmapi macros in the umount path
    
    Stop the flag saving as we never mangle those in the unmount path, and
    hide all the weird arguents to the dmapi code inside the
    XFS_SEND_PREUNMOUNT / XFS_SEND_UNMOUNT macros.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 0c3dc2b02a4996c13e26eb91296e8a309e0c6227
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:23 2009 +0000

    xfs: remove incorrect sparse annotation for xfs_iget_cache_miss
    
    xfs_iget_cache_miss does not get called with the pag_ici_lock held, so
    the __releases annotation is incorrect.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit b8f82a4a6fc79fcb4b2eb81252020e04c9b49da5
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:22 2009 +0000

    xfs: kill the STATIC_INLINE macro
    
    Remove our own STATIC_INLINE macro.  For small function inside
    implementation files just use STATIC and let gcc inline it, and for
    those in headers do the normal static inline - they are all small
    enough to be inlined for debug builds, too.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 5683f53e36235234f7861909fdff878ff1f1bb20
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:21 2009 +0000

    xfs: uninline xfs_get_extsz_hint
    
    This function is too large to efficiently be inlined.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit e82fa0c7ca29b805388aa51d3cad2cb7a4df3084
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:20 2009 +0000

    xfs: rename xfs_attr_fetch to xfs_attr_get_int
    
    Using a totally different name for the low-level get operation does
    not fit the _int convention used in the rest of the attr code, so
    rename it.
    
    While we're at it also fix the prototype to use the normal convention
    and mark it static as it's never used outside of xfs_attr.c.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 6ad112bfb5af537e9e3103c807748bb4a99bbd9e
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Tue Nov 24 18:02:23 2009 +0000

    xfs: simplify xfs_buf_get / xfs_buf_read interfaces
    
    Currently the low-level buffer cache interfaces are highly confusing
    as we have a _flags variant of each that does actually respect the
    flags, and one without _flags which has a flags argument that gets
    ignored and overriden with a default set.  Given that very few places
    use the default arguments get rid of the duplication and convert all
    callers to pass the flags explicitly.  Also remove the now confusing
    _flags postfix.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit c355c656fede21f6e967816a603905f0ad6a7311
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Sat Nov 14 16:17:18 2009 +0000

    xfs: remove IO_ISAIO
    
    We set the IO_ISAIO flag for all read/write I/O since early Linux
    2.6.x.  Remove it as it has lost it's purpose long ago.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Dave Chinner <david@xxxxxxxxxxxxx>
    Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit fc5bc4c85c45f0bf854404e5736aa8b65720a18d
Author: Andy Poling <andy@xxxxxxxxxxx>
Date:   Tue Nov 3 17:26:47 2009 +0000

    xfs: Wrapped journal record corruption on read at recovery
    
    Summary of problem:
    
    If a journal record wraps at the physical end of the journal, it has to be
    read in two parts in xlog_do_recovery_pass(): a read at the physical end 
and a
    read at the physical beginning.  If xlog_bread() has to re-align the first
    read, the second read request does not take that re-alignment into account.
    If the first read was re-aligned, the second read over-writes the end of the
    data from the first read, effectively corrupting it.  This can happen either
    when reading the record header or reading the record data.
    
    The first sanity check in xlog_recover_process_data() is to check for a 
valid
    clientid, so that is the error reported.
    
    Summary of fix:
    
    If there was a first read at the physical end, XFS_BUF_PTR() returns where 
the
    data was requested to begin.  Conversely, because it is the result of
    xlog_align(), offset indicates where the requested data for the first read
    actually begins - whether or not xlog_bread() has re-aligned it.
    
    Using offset as the base for the calculation of where to place the second 
read
    data ensures that it will be correctly placed immediately following the data
    from the first read instead of sometimes over-writing the end of it.
    
    The attached patch has resolved the reported problem of occasional inability
    to recover the journal (reporting "bad clientid").
    
    Signed-off-by: Andy Poling <andy@xxxxxxxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 5ec4fabb02fcb5b4a4154a27e4299af5aa0f87ac
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Fri Oct 30 09:11:47 2009 +0000

    xfs: cleanup data end I/O handlers
    
    Currently we have different end I/O handlers for read vs the different
    types of write I/O.  But they are all very similar so we could just
    use one with a few conditionals and reduce code size a lot.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 06342cf8adb23464deae0f58f8bcb87818a3bee6
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Fri Oct 30 09:09:15 2009 +0000

    xfs: use WRITE_SYNC_PLUG for synchronous writeout
    
    The VM and I/O schedulers now expect us to use WRITE_SYNC_PLUG for
    synchronous writeout.  Right now I can't see any changes in performance
    numbers with this, but we're getting some beating for not using it,
    and the knowledge definitely could help the block code to make better
    decisions.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 033da48fda9d56e28b3fe3ef87ef6fd43290f554
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Mon Oct 19 04:05:26 2009 +0000

    xfs: reset the i_iolock lock class in the reclaim path
    
    The iolock is used for protecting reads, writes and block truncates
    against each other.  We have two classes of callers, the first one is
    induced by a file operation and requires a reference to the inode be
    held and not dropped after the operation is done:
    
     - xfs_vm_vmap, xfs_vn_fallocate, xfs_read, xfs_write, xfs_splice_read,
       xfs_splice_write and xfs_setattr are all implementations of VFS
       methods that require a live inode
     - xfs_getbmap and xfs_swap_extents are ioctl subcommand for which the
       same is true
     - xfs_truncate_file is only called on quota inodes just returned from
       xfs_iget
     - xfs_sync_inode_data does the lock just after an igrab()
     - xfs_filestream_associate and xfs_filestream_new_ag take the iolock
       on the parent inode of an inode which by VFS rules must be referenced
    
    And we have various calls to truncate blocks past EOF or the whole
    file when dropping the last reference to an inode.  Unfortunately
    lockdep complains when we do memory allocations that can recurse into
    the filesystem in the first class because the second class happens to
    take the same lock.  To avoid this re-init the iolock in the beginning
    of xfs_fs_clear_inode to get a new lock class.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 80641dc66a2d6dfb22af4413227a92b8ab84c7bb
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Mon Oct 19 04:00:03 2009 +0000

    xfs: I/O completion handlers must use NOFS allocations
    
    When completing I/O requests we must not allow the memory allocator to
    recurse into the filesystem, as we might deadlock on waiting for the
    I/O completion otherwise.  The only thing currently allocating normal
    GFP_KERNEL memory is the allocation of the transaction structure for
    the unwritten extent conversion.  Add a memflags argument to
    _xfs_trans_alloc to allow controlling the allocator behaviour.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reported-by: Thomas Neumann <tneumann@xxxxxxxxxxxxxxxxxxxxx>
    Tested-by: Thomas Neumann <tneumann@xxxxxxxxxxxxxxxxxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit c56c9631cbe88f08854a56ff9776c1f310916830
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Mon Oct 19 04:03:46 2009 +0000

    xfs: fix mmap_sem/iolock inversion in xfs_free_eofblocks
    
    When xfs_free_eofblocks is called from ->release the VM might already
    hold the mmap_sem, but in the write path we take the iolock before
    taking the mmap_sem in the generic write code.
    
    Switch xfs_free_eofblocks to only trylock the iolock if called from
    ->release and skip trimming the prellocated blocks in that case.
    We'll still free them later on the final iput.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

commit 848ce8f731aed0a2d4ab5884a4f6664af73d2dd0
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:   Tue Sep 29 13:48:56 2009 +0000

    xfs: simplify inode teardown
    
    Currently the reclaim code for the case where we don't reclaim the
    final reclaim is overly complicated.  We know that the inode is clean
    but instead of just directly reclaiming the clean inode we go through
    the whole process of marking the inode reclaimable just to directly
    reclaim it from the calling context.  Besides being overly complicated
    this introduces a race where iget could recycle an inode between
    marked reclaimable and actually being reclaimed leading to panics.
    
    This patch gets rid of the existing reclaim path, and replaces it with
    a simple call to xfs_ireclaim if the inode was clean.  While we're at
    it we also use the slightly more lax xfs_inode_clean check we'd use
    later to determine if we need to flush the inode here.
    
    Finally get rid of xfs_reclaim function and place the remaining small
    bits of reclaim code directly into xfs_fs_destroy_inode.
    
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Reported-by: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
    Reported-by: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
    Tested-by: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
    Reviewed-by: Alex Elder <aelder@xxxxxxx>
    Signed-off-by: Alex Elder <aelder@xxxxxxx>

-----------------------------------------------------------------------

Summary of changes:


hooks/post-receive
-- 
XFS development tree

<Prev in Thread] Current Thread [Next in Thread>