1. 13 7月, 2008 1 次提交
  2. 25 6月, 2008 1 次提交
  3. 21 6月, 2008 1 次提交
  4. 13 6月, 2008 1 次提交
  5. 05 6月, 2008 1 次提交
  6. 27 5月, 2008 1 次提交
  7. 20 5月, 2008 1 次提交
  8. 19 5月, 2008 1 次提交
  9. 12 5月, 2008 1 次提交
  10. 11 5月, 2008 1 次提交
  11. 04 5月, 2008 1 次提交
  12. 02 5月, 2008 1 次提交
  13. 29 4月, 2008 2 次提交
  14. 26 4月, 2008 3 次提交
  15. 25 4月, 2008 1 次提交
  16. 24 4月, 2008 1 次提交
  17. 22 4月, 2008 1 次提交
  18. 17 4月, 2008 1 次提交
  19. 12 4月, 2008 1 次提交
  20. 02 4月, 2008 1 次提交
  21. 26 3月, 2008 1 次提交
  22. 24 3月, 2008 1 次提交
  23. 17 3月, 2008 1 次提交
  24. 10 3月, 2008 1 次提交
  25. 05 3月, 2008 1 次提交
  26. 25 2月, 2008 1 次提交
  27. 16 2月, 2008 1 次提交
  28. 15 2月, 2008 2 次提交
    • S
      kbuild: fix building vmlinux.o · cf87dcd1
      Sam Ravnborg 提交于
      Ingo Molnar wrote:
      >
      > i've got a build log from a weird build error below:
      >
      >   LD      init/built-in.o
      > distcc[12023] ERROR: compile (null) on localhost failed
      > make: *** [vmlinux.o] Error 1
      > make: *** Waiting for unfinished jobs....
      >   LD      .tmp_vmlinux1
      >
      
      Building vmlinux.o were moved up in the dependency chain so we started
      to build it before the kallsym stuff. This was done to let modpost
      report section mismatch bugs even when the final link failed.
      
      Originally I had expected the dependency of $(kallsyms.o) to
      cover this but it turns out that we need to be even more explicit.
      Fix this by adding a conditional dependency on firat target
      used in the kallsyms serie of builds.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Roland McGrath <roland@redhat.com>
      cf87dcd1
    • S
      kbuild: allow -fstack-protector to take effect · e06b8b98
      Sam Ravnborg 提交于
      Arjan van de Ven <arjan@infradead.org> wrote:
      ===
      I just read the excellent LWN writeup of the vmsplice
      security thing, and that got me wondering why this attack
      wasn't stopped by the CONFIG_CC_STACKPROTECTOR option...
      because it plain should have been...
      
      Some analysis later.. it turns out that the following line
      in the top level Makefile, added by you in October 2007,
      entirely disables CONFIG_CC_STACKPROTECTOR ;(
      With this line removed the exploit will be nicely stopped.
      
      CFLAGS          += $(call cc-option, -fno-stack-protector)
      
      Now I realize that certain distros have patched gcc to
      compensate for their lack of distro wide CFLAGS, and it's
      great to work around that... but would there be a way to NOT
      disable this for CONFIG_CC_STACKPROTECTOR please?
      It would have made this exploit not possible for those kernels
      that enable this feature (and that includes distros like Fedora)
      ===
      
      Move the assignment to KBUILD_CFLAGS up before including
      the arch specific Makefile so arch makefiles may override
      the setting.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Arjan van de Ven <arjan@infradead.org>
      Cc: stable@kernel.org
      e06b8b98
  29. 11 2月, 2008 1 次提交
    • L
      Linux 2.6.25-rc1 · 19af3554
      Linus Torvalds 提交于
      .. and I really need to call it something else.  Maybe it is time to
      bring back the weasel series, since weasels always make me feel good
      about a kernel.
      19af3554
  30. 03 2月, 2008 1 次提交
  31. 29 1月, 2008 6 次提交