1. 25 4月, 2008 1 次提交
  2. 24 4月, 2008 1 次提交
  3. 22 4月, 2008 1 次提交
  4. 17 4月, 2008 1 次提交
  5. 12 4月, 2008 1 次提交
  6. 02 4月, 2008 1 次提交
  7. 26 3月, 2008 1 次提交
  8. 24 3月, 2008 1 次提交
  9. 17 3月, 2008 1 次提交
  10. 10 3月, 2008 1 次提交
  11. 05 3月, 2008 1 次提交
  12. 25 2月, 2008 1 次提交
  13. 16 2月, 2008 1 次提交
  14. 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
  15. 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
  16. 03 2月, 2008 1 次提交
  17. 29 1月, 2008 9 次提交
  18. 28 1月, 2008 1 次提交
  19. 25 1月, 2008 1 次提交
  20. 22 1月, 2008 1 次提交
  21. 16 1月, 2008 1 次提交
  22. 07 1月, 2008 1 次提交
  23. 21 12月, 2007 1 次提交
  24. 11 12月, 2007 1 次提交
  25. 09 12月, 2007 2 次提交
    • S
      kbuild: fix building with O=.. options · 18c32dac
      Sam Ravnborg 提交于
      The check introduced in commit:
      4f1127e2 "kbuild: fix
      infinite make recursion"
      
      caused certain external modules not to build and
      also caused 'make targz-pkg' to fail.
      This is a minimal fix so we revert to previous
      behaviour - but we do not overwrite the Makefile
      in the top-level directory.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Tested-by: NJay Cliburn <jacliburn@bellsouth.net>
      Cc: Jay Cliburn <jacliburn@bellsouth.net>
      18c32dac
    • S
      kbuild: fix building with redirected output. · 1cacc9ab
      Sam Ravnborg 提交于
      Jan Altenberg <jan.altenberg@linutronix.de> reported that
      building with redirected input like this failed:
      make O=dir oldconfig bzImage < /dev/null
      
      The problem were caused by a make silentoldconfig being
      run before oldconfig and with a non-recent .config the build
      failed because silentoldconfig requires non-redirected stdin.
      
      Silentoldconfig was run as a side-effect of having the
      top-level Makefile re-made by make.
      Introducing an empty rule for the top-level Makefile
      (and Kbuild.include) fixed the issue.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      1cacc9ab
  26. 04 12月, 2007 1 次提交
  27. 18 11月, 2007 2 次提交
    • S
      x86: simplify "make ARCH=x86" and fix kconfig all.config · 6840999b
      Sam Ravnborg 提交于
      Simplify "make ARCH=x86" and fix kconfig so we again can set 64BIT in
      all.config.
      
      For a fix the diffstat is nice:
       6 files changed, 3 insertions(+), 36 deletions(-)
      
      The patch reverts these commits:
       - 0f855aa6 ("kconfig: add helper to set
         config symbol from environment variable")
       - 2a113281 ("kconfig: use $K64BIT to
         set 64BIT with all*config targets")
      
      Roman Zippel pointed out that kconfig supported string compares so
      the additional complexity introduced by the above two patches were
      not needed.
      
      With this patch we have following behaviour:
      
        # make {allno,allyes,allmod,rand}config [ARCH=...]
        option \ host arch      | 32bit         | 64bit
        =====================================================
        ./.                     | 32bit         | 64bit
        ARCH=x86                | 32bit         | 32bit
        ARCH=i386               | 32bit         | 32bit
        ARCH=x86_64             | 64bit         | 64bit
      
      The general rule are that ARCH= and native architecture takes
      precedence over the configuration.
      
      So make ARCH=i386 [whatever] will always build a 32-bit kernel
      no matter what the configuration says.  The configuration will
      be updated to 32-bit if it was configured to 64-bit and the
      other way around.
      
      This behaviour is consistent with previous behaviour so no
      suprises here.
      
      make ARCH=x86 will per default result in a 32-bit kernel but as
      the only ARCH= value x86 allow the user to select between 32-bit
      and 64-bit using menuconfig.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: Andreas Herrmann <aherrman@arcor.de>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6840999b
    • S
      x86: simplify "make ARCH=x86" and fix kconfig all.config · 80ef88d6
      Sam Ravnborg 提交于
      Simplify "make ARCH=x86" and fix kconfig so we again
      can set 64BIT in all.config.
      
      For a fix the diffstat is nice:
       6 files changed, 3 insertions(+), 36 deletions(-)
      
      The patch reverts these commits:
      0f855aa6
      -> kconfig: add helper to set config symbol from environment variable
      
      2a113281
      -> kconfig: use $K64BIT to set 64BIT with all*config targets
      
      Roman Zippel pointed out that kconfig supported string
      compares so the additional complexity introduced by the
      above two patches were not needed.
      
      With this patch we have following behaviour:
      
      # make {allno,allyes,allmod,rand}config [ARCH=...]
      option \ host arch      | 32bit         | 64bit
      =====================================================
      ./.                     | 32bit         | 64bit
      ARCH=x86                | 32bit         | 32bit
      ARCH=i386               | 32bit         | 32bit
      ARCH=x86_64             | 64bit         | 64bit
      
      The general rule are that ARCH= and native architecture
      takes precedence over the configuration.
      So make ARCH=i386 [whatever] will always build a 32-bit
      kernel no matter what the configuration says.
      The configuration will be updated to 32-bit if it was
      configured to 64-bit and the other way around.
      
      This behaviour is consistent with previous behaviour so
      no suprises here.
      
      make ARCH=x86 will per default result in a 32-bit kernel
      but as the only ARCH= value x86 allow the user to select
      between 32-bit and 64-bit using menuconfig. 
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: Andreas Herrmann <aherrman@arcor.de>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      80ef88d6
  28. 17 11月, 2007 2 次提交