1. 26 7月, 2007 3 次提交
  2. 24 7月, 2007 1 次提交
  3. 20 7月, 2007 6 次提交
  4. 18 7月, 2007 1 次提交
    • T
      kallsyms: make KSYM_NAME_LEN include space for trailing '\0' · 9281acea
      Tejun Heo 提交于
      KSYM_NAME_LEN is peculiar in that it does not include the space for the
      trailing '\0', forcing all users to use KSYM_NAME_LEN + 1 when allocating
      buffer.  This is nonsense and error-prone.  Moreover, when the caller
      forgets that it's very likely to subtly bite back by corrupting the stack
      because the last position of the buffer is always cleared to zero.
      
      This patch increments KSYM_NAME_LEN by one and updates code accordingly.
      
      * off-by-one bug in asm-powerpc/kprobes.h::kprobe_lookup_name() macro
        is fixed.
      
      * Where MODULE_NAME_LEN and KSYM_NAME_LEN were used together,
        MODULE_NAME_LEN was treated as if it didn't include space for the
        trailing '\0'.  Fix it.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Acked-by: NPaulo Marques <pmarques@grupopie.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9281acea
  5. 17 7月, 2007 26 次提交
  6. 07 7月, 2007 1 次提交
  7. 29 6月, 2007 1 次提交
    • D
      Introduce fixed sys_sync_file_range2() syscall, implement on PowerPC and ARM · edd5cd4a
      David Woodhouse 提交于
      Not all the world is an i386.  Many architectures need 64-bit arguments to be
      aligned in suitable pairs of registers, and the original
      sys_sync_file_range(int, loff_t, loff_t, int) was therefore wasting an
      argument register for padding after the first integer.  Since we don't
      normally have more than 6 arguments for system calls, that left no room for
      the final argument on some architectures.
      
      Fix this by introducing sys_sync_file_range2(int, int, loff_t, loff_t) which
      all fits nicely.  In fact, ARM already had that, but called it
      sys_arm_sync_file_range.  Move it to fs/sync.c and rename it, then implement
      the needed compatibility routine.  And stop the missing syscall check from
      bitching about the absence of sys_sync_file_range() if we've implemented
      sys_sync_file_range2() instead.
      
      Tested on PPC32 and with 32-bit and 64-bit userspace on PPC64.
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      edd5cd4a
  8. 24 6月, 2007 1 次提交
    • A
      update checkpatch.pl to version 0.06 · d8aaf121
      Andy Whitcroft 提交于
      Update to checkpatch.pl v0.06.  Of note:
      
       - do { and else handled correctly as control structures for { matching
       - trailing whitespace correctly tripped when line otherwise empty
       - support for const, including const foo * const bar
       - multiline macros defining values correctly reported
      
      This version of checkpatch.pl can be found at the following URL:
      
      http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-0.06
      
      Full Changelog:
      
      Andy Whitcroft (14):
            Version: 0.06
            cleanup the Type regular expression declarations
            fix up block counting
            end of line counts as a space for ++ and --
            do { needs the same checks as if, for et al
            handle "const foo * const a" as a valid type
            add spacing checks following ;
            complete whitespace lines should trip trailing whitespace check
            else is also a block control structure
            badly formatted else can trip function declaration
            detect and report trailing statements after else
            types need to be terminated by a boundary
            multiline macros defining values should be surrounded by parentheses
            soften the wording of the Signed-off-by: warnings
      Signed-off-by: NAndy Whitcroft <apw@shadowen.org>
      Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d8aaf121