Doug / smarc-fsl-linux-kernel

15 Mar, 2009

1 commit

07 Mar, 2009

1 commit

  • 7bf446f8b   xfs: include header files for prototypes ... Browse Code »

    Fix this sparse warnings:
    fs/xfs/linux-2.6/xfs_ioctl.c:72:1: warning: symbol 'xfs_find_handle' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:249:1: warning: symbol 'xfs_open_by_handle' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:361:1: warning: symbol 'xfs_readlink_by_handle' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:496:1: warning: symbol 'xfs_attrmulti_attr_get' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:525:1: warning: symbol 'xfs_attrmulti_attr_set' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:555:1: warning: symbol 'xfs_attrmulti_attr_remove' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:657:1: warning: symbol 'xfs_ioc_space' was not declared. Should it be static?
    fs/xfs/linux-2.6/xfs_ioctl.c:1340:1: warning: symbol 'xfs_file_ioctl' was not declared. Should it be static?
    fs/xfs/support/debug.c:65:1: warning: symbol 'xfs_fs_vcmn_err' was not declared. Should it be static?
    fs/xfs/support/debug.c:112:1: warning: symbol 'xfs_hex_dump' was not declared. Should it be static?

    Signed-off-by: Hannes Eder
    Reviewed-by: Christoph Hellwig
    Signed-off-by: Felix Blyakher

    Hannes Eder
     

22 Dec, 2008

1 commit

  • efc557570   [XFS] avoid memory allocations in xfs_fs_vcmn_err ... Browse Code »

    xfs_fs_vcmn_err can be called under a spinlock, but does a sleeping memory
    allocation to create buffer for it's internal sprintf. Fortunately it's
    the only caller of icmn_err, so we can merge the two and have one single
    static buffer and spinlock protecting it. While we're at it make sure
    we proper __attribute__ format annotations so that the compiler can detect
    mismatched format strings.

    Reported-by: Alexander Beregalov
    Signed-off-by: Christoph Hellwig
    Reviewed-by: Eric Sandeen
    Signed-off-by: Lachlan McIlroy

    Christoph Hellwig
     

30 Oct, 2008

1 commit

07 Feb, 2008

2 commits

  • d4f3cc016   [XFS] lose xfs_hex_dump in favor of print_hex_dump ... Browse Code »

    No need for xfs to have its own hex dumping routine now that the kernel
    has one.

    SGI-PV: 971186
    SGI-Modid: xfs-linux-melb:xfs-kern:29847a

    Signed-off-by: Eric Sandeen
    Signed-off-by: Lachlan McIlroy
    Signed-off-by: Tim Shimmin

    Eric Sandeen
     
  • 007c61c68   [XFS] Remove spin.h ... Browse Code »

    remove spinlock init abstraction macro in spin.h, remove the callers, and
    remove the file. Move no-op spinlock_destroy to xfs_linux.h Cleanup
    spinlock locals in xfs_mount.c

    SGI-PV: 970382
    SGI-Modid: xfs-linux-melb:xfs-kern:29751a

    Signed-off-by: Eric Sandeen
    Signed-off-by: Donald Douwsma
    Signed-off-by: Lachlan McIlroy
    Signed-off-by: Tim Shimmin

    Eric Sandeen
     

08 May, 2007

1 commit

10 Feb, 2007

1 commit

  • dc74eaad8   [XFS] Prevent buffer overrun in cmn_err(). ... Browse Code »

    The message buffer used by cmn_err() is only 256 bytes and some CXFS
    messages were exceeding this length. Since we were using vsprintf() and
    not checking for buffer overruns we were clobbering memory beyond the
    buffer. The size of the buffer has been increased to 1024 bytes so we can
    capture these larger messages and we are now using vsnprintf() to prevent
    overrunning the buffer size.

    SGI-PV: 958599
    SGI-Modid: xfs-linux-melb:xfs-kern:27561a

    Signed-off-by: Lachlan McIlroy
    Signed-off-by: Geoffrey Wehrman
    Signed-off-by: Tim Shimmin

    Lachlan McIlroy
     

11 Nov, 2006

1 commit

04 Oct, 2006

1 commit

09 Jun, 2006

1 commit

12 Jan, 2006

1 commit

11 Jan, 2006

1 commit

02 Nov, 2005

1 commit

05 Sep, 2005

1 commit

21 Jun, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds