1. 20 4月, 2013 1 次提交
    • D
      irda: small read past the end of array in debug code · e15465e1
      Dan Carpenter 提交于
      The "reason" can come from skb->data[] and it hasn't been capped so it
      can be from 0-255 instead of just 0-6.  For example in irlmp_state_dtr()
      the code does:
      
      	reason = skb->data[3];
      	...
      	irlmp_disconnect_indication(self, reason, skb);
      
      Also LMREASON has a couple other values which don't have entries in the
      irlmp_reasons[] array.  And 0xff is a valid reason as well which means
      "unknown".
      
      So far as I can see we don't actually care about "reason" except for in
      the debug code.
      Signed-off-by: NDan Carpenter <dan.carpenter@oracle.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e15465e1
  2. 28 2月, 2013 1 次提交
  3. 17 6月, 2011 1 次提交
  4. 07 6月, 2011 1 次提交
  5. 28 3月, 2011 1 次提交
  6. 11 10月, 2010 1 次提交
  7. 18 5月, 2010 1 次提交
  8. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  9. 06 8月, 2009 1 次提交
  10. 03 5月, 2008 1 次提交
  11. 06 3月, 2008 1 次提交
  12. 29 1月, 2008 1 次提交
  13. 20 11月, 2007 1 次提交
  14. 20 10月, 2007 1 次提交
  15. 18 7月, 2007 1 次提交
    • S
      [IrDA]: Fix IrDA build failure · 75a69ac6
      Samuel Ortiz 提交于
      When having built-in IrDA, we hit the following error:
      
      `irda_sysctl_unregister' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irda_proc_unregister' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irsock_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irttp_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `iriap_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irda_device_cleanup' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irlap_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irlmp_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      make[1]: *** [.tmp_vmlinux1] Error 1
      make: *** [_all] Error 2
      
      This is due to the irda_init fix recently added, where we call __exit
      routines from an __init one. It is a build failure that I didn't catch
      because it doesn't show up when building IrDA as a module. My apologies
      for that.
      The following patch fixes that failure and is against your net-2.6
      tree. I hope it can make it to the merge window, and stable@kernel.org
      is CCed on this mail.
      Signed-off-by: NSamuel Ortiz <samuel@sortiz.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      75a69ac6
  16. 11 7月, 2007 1 次提交
  17. 13 2月, 2007 1 次提交
  18. 11 2月, 2007 1 次提交
  19. 04 12月, 2006 1 次提交
  20. 03 12月, 2006 2 次提交
  21. 29 9月, 2006 1 次提交
  22. 22 7月, 2006 1 次提交
  23. 01 7月, 2006 1 次提交
  24. 23 5月, 2006 1 次提交
  25. 03 1月, 2006 1 次提交
  26. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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!
      1da177e4