1. 25 Apr, 2014 1 commit
  2. 07 Apr, 2014 1 commit
  3. 26 Feb, 2014 1 commit
  4. 23 Jan, 2014 1 commit
    • Vivek Goyal's avatar
      kdump: fix exported size of vmcoreinfo note · 77019967
      Vivek Goyal authored
      Right now we seem to be exporting the max data size contained inside
      vmcoreinfo note.  But this does not include the size of meta data around
      vmcore info data.  Like name of the note and starting and ending elf_note.
      I think user space expects total size and that size is put in PT_NOTE elf
      header.  Things seem to be fine so far because we are not using vmcoreinfo
      note to the maximum capacity.  But as it starts filling up, to capacity,
      at some point of time, problem will be visible.
      I don't think user space will be broken with this change.  So there is no
      need to introduce vmcoreinfo2.  This change is safe and backward
      compatible.  More explanation on why this change is safe is below.
      vmcoreinfo contains information about kernel which user space needs to
      know to do things like filtering.  For example, various kernel config
      options or information about size or offset of some data structures etc.
      All this information is commmunicated to user space with an ELF note
      present in ELF /proc/vmcore file.
      Currently vmcoreinfo data size is 4096.  With some elf note meta data
      around it, actual size is 4132 bytes.  But we are using barely 25% of that
      size.  Rest is empty.  So even if we tell user space that size of ELf note
      is 4096 and not 4132, nothing will be broken becase after around 1000
      bytes, everything is zero anyway.
      But once we start filling up the note to the capacity, and not report the
      full size of note, bad things will start happening.  Either some data will
      be lost or tools will be confused that they did not fine the zero note at
      the end.
      So I think this change is safe and should not break existing tools.
      Signed-off-by: default avatarVivek Goyal <vgoyal@redhat.com>
      Cc: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
      Cc: Dan Aloni <da-x@monatomic.org>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  5. 12 Sep, 2013 1 commit
  6. 28 Nov, 2012 1 commit
  7. 23 Oct, 2012 1 commit
  8. 31 Oct, 2011 2 commits
  9. 19 Apr, 2011 1 commit
  10. 21 May, 2010 1 commit
  11. 05 Feb, 2010 1 commit
  12. 21 Jan, 2010 1 commit
  13. 16 Dec, 2009 1 commit
  14. 06 Jan, 2009 1 commit
  15. 16 Oct, 2008 1 commit
  16. 24 Jan, 2008 6 commits
  17. 17 Oct, 2007 2 commits
  18. 15 Oct, 2007 1 commit
  19. 20 Jul, 2007 1 commit
    • David Howells's avatar
      FRV: Fix linkage problems · 0b1937ac
      David Howells authored
      Make it possible to use __start_notes and __stop_notes without getting a GPREL
      overflow error from the FRV linker.
      Small variables that would otherwise be in .data or .bss may, depending on the
      arch, be placed in special sections (.sdata or .sbss) that permit single
      instruction references on fixed instruction width machines.
      __start_notes and __stop_notes aren't really char variables, and certainly
      don't refer to data in .data or .bss.  Making them type "void" fools the
      compiler into not assuming anything about them.
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  20. 19 Jul, 2007 1 commit
    • Roland McGrath's avatar
      Add /sys/kernel/notes · da1a679c
      Roland McGrath authored
      This patch adds the /sys/kernel/notes magic file.  Reading this delivers the
      contents of the kernel's .notes section.  This lets userland easily glean any
      detailed information about the running kernel's build that was stored there at
      compile time.
      Signed-off-by: default avatarRoland McGrath <roland@redhat.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  21. 02 May, 2007 1 commit
  22. 30 Jun, 2006 1 commit
  23. 23 Jun, 2006 1 commit
  24. 24 Mar, 2006 1 commit
  25. 20 Mar, 2006 1 commit
  26. 10 Jan, 2006 1 commit
  27. 04 Jan, 2006 3 commits
    • akpm@osdl.org's avatar
      [PATCH] kobject_uevent CONFIG_NET=n fix · f743ca5e
      akpm@osdl.org authored
      lib/lib.a(kobject_uevent.o)(.text+0x25f): In function `kobject_uevent':
      : undefined reference to `__alloc_skb'
      lib/lib.a(kobject_uevent.o)(.text+0x2a1): In function `kobject_uevent':
      : undefined reference to `skb_over_panic'
      lib/lib.a(kobject_uevent.o)(.text+0x31d): In function `kobject_uevent':
      : undefined reference to `skb_over_panic'
      lib/lib.a(kobject_uevent.o)(.text+0x356): In function `kobject_uevent':
      : undefined reference to `netlink_broadcast'
      lib/lib.a(kobject_uevent.o)(.init.text+0x9): In function `kobject_uevent_init':
      : undefined reference to `netlink_kernel_create'
      make: *** [.tmp_vmlinux1] Error 1
      Netlink is unconditionally enabled if CONFIG_NET, so that's OK.
      kobject_uevent.o is compiled even if !CONFIG_HOTPLUG, which is lazy.
      Let's compound the sin.
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Kay Sievers's avatar
      [PATCH] driver core: replace "hotplug" by "uevent" · 312c004d
      Kay Sievers authored
      Leave the overloaded "hotplug" word to susbsystems which are handling
      real devices. The driver core does not "plug" anything, it just exports
      the state to userspace and generates events.
      Signed-off-by: default avatarKay Sievers <kay.sievers@suse.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Kay Sievers's avatar
      [PATCH] add uevent_helper control in /sys/kernel/ · 0f76e5ac
      Kay Sievers authored
      This deprecates the /proc/sys/kernel/hotplug file, as all
      this stuff should be in /sys some day, right? :)
      In /sys/kernel/ we have now uevent_seqnum and uevent_helper.
      The seqnum is no longer used by udev, as the version for this
      kernel depends on netlink which events will never get
      Recent udev versions disable the /sbin/hotplug helper with
      an init script, cause it leads to OOM on big boxes by running
      hundreds of shells in parallel. It should be done now by:
        echo "" > /sys/kernel/uevent_helper
      (Note that "-n" does not work, cause neighter proc nor sysfs
      support truncate().)
      Signed-off-by: default avatarKay Sievers <kay.sievers@suse.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
  28. 25 Jun, 2005 1 commit
  29. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!