Eric Lee / smarc-fsl-linux-kernel

27 Jul, 2007

1 commit

12 Feb, 2007

1 commit

  • 0a7b35cb1   [PATCH] Add retain_initrd boot option ... Browse Code »

    Add retain_initrd option to control freeing of initrd memory after
    extraction. By default, free memory as previously.

    The first boot will need to hold a copy of the in memory fs for the second
    boot. This image can be large (much larger than the kernel), hence we can
    save time when the memory loader is slow. Also, it reduces the memory
    footprint while extracting the first boot since you don't need another copy
    of the fs.

    Signed-off-by: Michael Neuling
    Cc: "Randy.Dunlap"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Michael Neuling
     

12 Dec, 2006

1 commit

08 Dec, 2006

1 commit

  • 2e591bbc0   [PATCH] Make initramfs printk a warning on incorrect cpio type ... Browse Code »

    It turns out that the "-c" option of cpio is highly unportable even between
    distros let alone unix variants, and may actually make the wrong type of
    cpio archive. I just wasted quite some time on this, and the kernel can
    detect this and warn about it (it's __init memory so it gets thrown away
    and thus there is no runtime overhead)

    Signed-off-by: Arjan van de Ven
    Cc: Al Viro
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arjan van de Ven
     

27 Jun, 2006

1 commit

  • 2139a7fbf   [PATCH] initramfs overwrite fix ... Browse Code »

    This patch ensures that initramfs overwrites work correctly, even when dealing
    with device nodes of different types. Furthermore, when replacing a file
    which already exists, we must make very certain that we truncate the existing
    file.

    Signed-off-by: H. Peter Anvin
    Cc: Michael Neuling
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    H. Peter Anvin
     

16 May, 2006

1 commit

  • 6a050da45   [PATCH] initramfs: fix CPIO hardlink check ... Browse Code »

    Copy the filenames of hardlinks when inserting them into the hash, since
    the "name" pointer may point to scratch space (name_buf). Not doing so
    results in corruption if the scratch space is later overwritten: the wrong
    file may be hardlinked, or, if the scratch space contains garbage, the link
    will fail and a 0-byte file will be created instead.

    Signed-off-by: Mark Huang
    Acked-by: Al Viro
    Cc: "H. Peter Anvin"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mark Huang
     

27 Mar, 2006

1 commit

26 Mar, 2006

1 commit

  • 340e48e66   [PATCH] BLK_DEV_INITRD: do not require BLK_DEV_RAM=y ... Browse Code »

    Initramfs initrd images do not need a ramdisk device, so remove this
    restriction in Kconfig. BLK_DEV_RAM=n saves about 13k on i386. Also
    without ramdisk device there's no need for "dry run", so initramfs unpacks
    much faster.

    People using cramfs, squashfs, or gzipped ext2/minix initrd images are
    probably smart enough not to turn off ramdisk support by accident.

    Cc: Al Viro
    Cc: Christoph Hellwig
    Cc: "H. Peter Anvin"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Zdenek Pavlas
     

11 Feb, 2006

1 commit

  • 9c15e852a   [PATCH] kexec: fix in free initrd when overlapped with crashkernel region ... Browse Code »

    It is possible that the reserved crashkernel region can be overlapped with
    initrd since the bootloader sets the initrd location. When the initrd
    region is freed, the second kernel memory will not be contiguous. The
    Kexec_load can cause an oops since there is no contiguous memory to write
    the second kernel or this memory could be used in the first kernel itself
    and may not be part of the dump. For example, on powerpc, the initrd is
    located at 36MB and the crashkernel starts at 32MB. The kexec_load caused
    panic since writing into non-allocated memory (after 36MB). We could see
    the similar issue even on other archs.

    One possibility is to move the initrd outside of crashkernel region. But,
    the initrd region will be freed anyway before the system is up. This patch
    fixes this issue and frees only regions that are not part of crashkernel
    memory in case overlaps.

    Signed-off-by: Haren Myneni
    Acked-by: "Eric W. Biederman"
    Cc: Vivek Goyal
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Haren Myneni
     

13 Sep, 2005

1 commit

  • 0f3d2bd54   [PATCH] free initrd mem adjustment ... Browse Code »

    Besides freeing initrd memory, also clear out the now dangling pointers to
    it, to make sure accidental late use attempts can be detected.

    Signed-off-by: Jan Beulich
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jan Beulich
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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