xfs
[Top] [All Lists]

[XFS updates] XFS development tree branch, master, updated. for-linus-v3

To: xfs@xxxxxxxxxxx
Subject: [XFS updates] XFS development tree branch, master, updated. for-linus-v3.10-rc1-2-14680-gf722406
From: xfs@xxxxxxxxxxx
Date: Wed, 15 May 2013 16:59:22 -0500 (CDT)
Delivered-to: xfs@xxxxxxxxxxx
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
  8769e07 Merge tag 'for-linus-v3.10-rc1-2' of git://oss.sgi.com/xfs/xfs
  a27bb33 aio: don't include aio.h in sched.h
  c8d8566 Merge tag 'for-linus-v3.10-rc1' of git://oss.sgi.com/xfs/xfs
  8d71db4 lift sb_start_write/sb_end_write out of ->aio_write()
  10b3866 Merge tag 'for-linus-v3.9-rc4' of git://oss.sgi.com/xfs/xfs
  e001873 xfs: ensure we capture IO errors correctly
  3325bee xfs: fix xfs_iomap_eof_prealloc_initial_size type
  83cdadd xfs: fix potential infinite loop in xfs_iomap_prealloc_size()
  7f78e03 fs: Limit sys_mount to only request filesystem modules.
      from  7dfbcbefad4b24d9822d04dbd7b5dd5c3fd45076 (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 8769e078a9a2bce13d39c08e0e5a513f5320e1de
Merge: 8cbc95e 7dfbcbe
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date:   Thu May 9 13:06:20 2013 -0700

    Merge tag 'for-linus-v3.10-rc1-2' of git://oss.sgi.com/xfs/xfs
    
    Pull xfs update (#2) from Ben Myers:
    
     - add CONFIG_XFS_WARN, a step between zero debugging and
       CONFIG_XFS_DEBUG.
    
     - fix attrmulti and attrlist to fall back to vmalloc when kmalloc
       fails.
    
    * tag 'for-linus-v3.10-rc1-2' of git://oss.sgi.com/xfs/xfs:
      xfs: fallback to vmalloc for large buffers in 
xfs_compat_attrlist_by_handle
      xfs: fallback to vmalloc for large buffers in xfs_attrlist_by_handle
      xfs: introduce CONFIG_XFS_WARN

commit a27bb332c04cec8c4afd7912df0dc7890db27560
Author: Kent Overstreet <koverstreet@xxxxxxxxxx>
Date:   Tue May 7 16:19:08 2013 -0700

    aio: don't include aio.h in sched.h
    
    Faster kernel compiles by way of fewer unnecessary includes.
    
    [akpm@xxxxxxxxxxxxxxxxxxxx: fix fallout]
    [akpm@xxxxxxxxxxxxxxxxxxxx: fix build]
    Signed-off-by: Kent Overstreet <koverstreet@xxxxxxxxxx>
    Cc: Zach Brown <zab@xxxxxxxxxx>
    Cc: Felipe Balbi <balbi@xxxxxx>
    Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    Cc: Mark Fasheh <mfasheh@xxxxxxxx>
    Cc: Joel Becker <jlbec@xxxxxxxxxxxx>
    Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
    Cc: Jens Axboe <axboe@xxxxxxxxx>
    Cc: Asai Thambi S P <asamymuthupa@xxxxxxxxxx>
    Cc: Selvan Mani <smani@xxxxxxxxxx>
    Cc: Sam Bradshaw <sbradshaw@xxxxxxxxxx>
    Cc: Jeff Moyer <jmoyer@xxxxxxxxxx>
    Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
    Cc: Benjamin LaHaise <bcrl@xxxxxxxxx>
    Reviewed-by: "Theodore Ts'o" <tytso@xxxxxxx>
    Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

commit c8d8566952fda026966784a62f324c8352f77430
Merge: a9586d9 cab09a8
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date:   Thu May 2 14:49:33 2013 -0700

    Merge tag 'for-linus-v3.10-rc1' of git://oss.sgi.com/xfs/xfs
    
    Pull xfs update from Ben Myers:
     "For 3.10-rc1 we have a number of bug fixes and cleanups and a
      currently experimental feature from David Chinner, CRCs protection for
      metadata.  CRCs are enabled by using mkfs.xfs to create a filesystem
      with the feature bits set.
    
       - numerous fixes for speculative preallocation
       - don't verify buffers on IO errors
       - rename of random32 to prandom32
       - refactoring/rearrangement in xfs_bmap.c
       - removal of unused m_inode_shrink in struct xfs_mount
       - fix error handling of xfs_bufs and readahead
       - quota driven preallocation throttling
       - fix WARN_ON in xfs_vm_releasepage
       - add ratelimited printk for different alert levels
       - fix spurious forced shutdowns due to freed Extent Free Intents
       - remove some obsolete XLOG_CIL_HARD_SPACE_LIMIT() macros
       - remove some obsoleted comments
       - (experimental) CRC support for metadata"
    
    * tag 'for-linus-v3.10-rc1' of git://oss.sgi.com/xfs/xfs: (46 commits)
      xfs: fix da node magic number mismatches
      xfs: Remote attr validation fixes and optimisations
      xfs: Teach dquot recovery about CONFIG_XFS_QUOTA
      xfs: add metadata CRC documentation
      xfs: implement extended feature masks
      xfs: add CRC checks to the superblock
      xfs: buffer type overruns blf_flags field
      xfs: add buffer types to directory and attribute buffers
      xfs: add CRC protection to remote attributes
      xfs: split remote attribute code out
      xfs: add CRCs to attr leaf blocks
      xfs: add CRCs to dir2/da node blocks
      xfs: shortform directory offsets change for dir3 format
      xfs: add CRC checking to dir2 leaf blocks
      xfs: add CRC checking to dir2 data blocks
      xfs: add CRC checking to dir2 free blocks
      xfs: add CRC checks to block format directory blocks
      xfs: add CRC checks to remote symlinks
      xfs: split out symlink code into it's own file.
      xfs: add version 3 inode format with CRCs
      ...

commit 8d71db4f0890605d44815a2b2da4ca003f1bb142
Author: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date:   Tue Mar 19 21:01:03 2013 -0400

    lift sb_start_write/sb_end_write out of ->aio_write()
    
    Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>

commit 10b38669d64c757cfd927e3820292c580ed70aae
Merge: 547b524 e001873
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date:   Tue Mar 19 15:17:40 2013 -0700

    Merge tag 'for-linus-v3.9-rc4' of git://oss.sgi.com/xfs/xfs
    
    Pull XFS fixes from Ben Myers:
    
     - Fix for a potential infinite loop which was introduced in commit
       4d559a3bcb73 ("xfs: limit speculative prealloc near ENOSPC
       thresholds")
    
     - Fix for the return type of xfs_iomap_eof_prealloc_initial_size from
       commit a1e16c26660b ("xfs: limit speculative prealloc size on sparse
       files")
    
     - Fix for a failed buffer readahead causing subsequent callers to fail
       incorrectly
    
    * tag 'for-linus-v3.9-rc4' of git://oss.sgi.com/xfs/xfs:
      xfs: ensure we capture IO errors correctly
      xfs: fix xfs_iomap_eof_prealloc_initial_size type
      xfs: fix potential infinite loop in xfs_iomap_prealloc_size()

commit e001873853d87674dd5b3cfa2851885023616695
Author: Dave Chinner <dchinner@xxxxxxxxxx>
Date:   Tue Mar 12 23:30:34 2013 +1100

    xfs: ensure we capture IO errors correctly
    
    Failed buffer readahead can leave the buffer in the cache marked
    with an error. Most callers that then issue a subsequent read on the
    buffer do not zero the b_error field out, and so we may incorectly
    detect an error during IO completion due to the stale error value
    left on the buffer.
    
    Avoid this problem by zeroing the error before IO submission. This
    ensures that the only IO errors that are detected those captured
    from are those captured from bio submission or completion.
    
    Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Reviewed-by: Mark Tinguely <tinguely@xxxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>
    
    (cherry picked from commit c163f9a1760229a95d04e37b332de7d5c1c225cd)

commit 3325beed46d8d14d873e94d89ea57ee900dec942
Author: Mark Tinguely <tinguely@xxxxxxx>
Date:   Sun Feb 24 13:04:37 2013 -0600

    xfs: fix xfs_iomap_eof_prealloc_initial_size type
    
    Fix the return type of xfs_iomap_eof_prealloc_initial_size() to
    xfs_fsblock_t to reflect the fact that the return value may be an
    unsigned 64 bits if XFS_BIG_BLKNOS is defined.
    
    Signed-off-by: Mark Tinguely <tinguely@xxxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>
    
    (cherry picked from commit e8108cedb1c5d1dc359690d18ca997e97a0061d2)

commit 83cdadd8b0559c93728d065d23ca3485fa567e54
Author: Brian Foster <bfoster@xxxxxxxxxx>
Date:   Fri Feb 22 13:32:56 2013 -0500

    xfs: fix potential infinite loop in xfs_iomap_prealloc_size()
    
    If freesp == 0, we could end up in an infinite loop while squashing
    the preallocation. Break the loop when we've killed the prealloc
    entirely.
    
    Signed-off-by: Brian Foster <bfoster@xxxxxxxxxx>
    Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
    Signed-off-by: Ben Myers <bpm@xxxxxxx>
    
    (cherry picked from commit e78c420bfc2608bb5f9a0b9165b1071c1e31166a)

commit 7f78e0351394052e1a6293e175825eb5c7869507
Author: Eric W. Biederman <ebiederm@xxxxxxxxxxxx>
Date:   Sat Mar 2 19:39:14 2013 -0800

    fs: Limit sys_mount to only request filesystem modules.
    
    Modify the request_module to prefix the file system type with "fs-"
    and add aliases to all of the filesystems that can be built as modules
    to match.
    
    A common practice is to build all of the kernel code and leave code
    that is not commonly needed as modules, with the result that many
    users are exposed to any bug anywhere in the kernel.
    
    Looking for filesystems with a fs- prefix limits the pool of possible
    modules that can be loaded by mount to just filesystems trivially
    making things safer with no real cost.
    
    Using aliases means user space can control the policy of which
    filesystem modules are auto-loaded by editing /etc/modprobe.d/*.conf
    with blacklist and alias directives.  Allowing simple, safe,
    well understood work-arounds to known problematic software.
    
    This also addresses a rare but unfortunate problem where the filesystem
    name is not the same as it's module name and module auto-loading
    would not work.  While writing this patch I saw a handful of such
    cases.  The most significant being autofs that lives in the module
    autofs4.
    
    This is relevant to user namespaces because we can reach the request
    module in get_fs_type() without having any special permissions, and
    people get uncomfortable when a user specified string (in this case
    the filesystem type) goes all of the way to request_module.
    
    After having looked at this issue I don't think there is any
    particular reason to perform any filtering or permission checks beyond
    making it clear in the module request that we want a filesystem
    module.  The common pattern in the kernel is to call request_module()
    without regards to the users permissions.  In general all a filesystem
    module does once loaded is call register_filesystem() and go to sleep.
    Which means there is not much attack surface exposed by loading a
    filesytem module unless the filesystem is mounted.  In a user
    namespace filesystems are not mounted unless .fs_flags = FS_USERNS_MOUNT,
    which most filesystems do not set today.
    
    Acked-by: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
    Acked-by: Kees Cook <keescook@xxxxxxxxxxxx>
    Reported-by: Kees Cook <keescook@xxxxxxxxxx>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>

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

Summary of changes:
 fs/xfs/xfs_aops.c  | 1 +
 fs/xfs/xfs_file.c  | 4 +---
 fs/xfs/xfs_super.c | 1 +
 3 files changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
XFS development tree

<Prev in Thread] Current Thread [Next in Thread>
  • [XFS updates] XFS development tree branch, master, updated. for-linus-v3.10-rc1-2-14680-gf722406, xfs <=