12 Dec, 2009

1 commit


09 May, 2008

1 commit

  • Don't allow a module built without versions altogether to be inserted
    into a kernel which expects modversions.

    modprobe --force will strip vermagic as well as modversions, so it
    won't be effected, but this will make sure that a
    non-CONFIG_MODVERSIONS module won't be accidentally inserted into a
    CONFIG_MODVERSIONS kernel.

    Signed-off-by: Rusty Russell
    Signed-off-by: Linus Torvalds

    Rusty Russell
     

26 Sep, 2006

1 commit


04 Jul, 2006

1 commit

  • include/linux/version.h contained both actual KERNEL version
    and UTS_RELEASE that contains a subset from git SHA1 for when
    kernel was compiled as part of a git repository.
    This had the unfortunate side-effect that all files including version.h
    would be recompiled when some git changes was made due to changes SHA1.
    Split it out so we keep independent parts in separate files.

    Also update checkversion.pl script to no longer check for UTS_RELEASE.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

11 Apr, 2006

1 commit

  • An UML user reported (against 2.6.13.3/UML) he got kernel Oopses when
    trying to rmmod (on a kernel with module unloading enabled) a module
    compiled with module unloading disabled. As crashing is a very correct
    thing to do in that case, a solution is altering the vermagic string to
    include this too.

    Possibly, however, the code should not crash in this case, even if the
    module didn't support unloading - it should simply abort the module
    removal. In this case, fixing that bug would be a better solution. I've
    not investigated though.

    (akpm: a bit marginal - root screwed up and shot himself in the foot).

    Cc: Hayim Shaul
    Cc: Rusty Russell
    Signed-off-by: Paolo 'Blaisorblade' Giarrusso
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Paolo 'Blaisorblade' Giarrusso
     

17 Apr, 2005

1 commit

  • 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