1. 02 12月, 2014 2 次提交
  2. 04 11月, 2014 1 次提交
  3. 01 11月, 2014 2 次提交
  4. 29 10月, 2014 1 次提交
  5. 28 10月, 2014 2 次提交
  6. 27 10月, 2014 1 次提交
  7. 25 10月, 2014 4 次提交
  8. 24 10月, 2014 2 次提交
  9. 23 10月, 2014 1 次提交
  10. 22 10月, 2014 1 次提交
  11. 21 10月, 2014 10 次提交
  12. 20 10月, 2014 1 次提交
  13. 16 10月, 2014 6 次提交
  14. 15 10月, 2014 3 次提交
  15. 14 10月, 2014 3 次提交
    • A
      lib/vsprintf: add %*pE[achnops] format specifier · 71dca95d
      Andy Shevchenko 提交于
      This allows user to print a given buffer as an escaped string.  The
      rules are applied according to an optional mix of flags provided by
      additional format letters.
      
      For example, if the given buffer is:
      
          1b 62 20 5c 43 07 22 90 0d 5d
      
      The result strings would be:
          %*pE            "\eb \C\a"\220\r]"
          %*pEhp          "\x1bb \C\x07"\x90\x0d]"
          %*pEa           "\e\142\040\\\103\a\042\220\r\135"
      
      Please, read Documentation/printk-formats.txt and lib/string_helpers.c
      kernel documentation to get further information.
      
      [akpm@linux-foundation.org: tidy up comment layout, per Joe]
      Signed-off-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Suggested-by: NJoe Perches <joe@perches.com>
      Cc: "John W . Linville" <linville@tuxdriver.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      71dca95d
    • O
      coredump: add %i/%I in core_pattern to report the tid of the crashed thread · b03023ec
      Oleg Nesterov 提交于
      format_corename() can only pass the leader's pid to the core handler,
      but there is no simple way to figure out which thread originated the
      coredump.
      
      As Jan explains, this also means that there is no simple way to create
      the backtrace of the crashed process:
      
      As programs are mostly compiled with implicit gcc -fomit-frame-pointer
      one needs program's .eh_frame section (equivalently PT_GNU_EH_FRAME
      segment) or .debug_frame section.  .debug_frame usually is present only
      in separate debug info files usually not even installed on the system.
      While .eh_frame is a part of the executable/library (and it is even
      always mapped for C++ exceptions unwinding) it no longer has to be
      present anywhere on the disk as the program could be upgraded in the
      meantime and the running instance has its executable file already
      unlinked from disk.
      
      One possibility is to echo 0x3f >/proc/*/coredump_filter and dump all
      the file-backed memory including the executable's .eh_frame section.
      But that can create huge core files, for example even due to mmapped
      data files.
      
      Other possibility would be to read .eh_frame from /proc/PID/mem at the
      core_pattern handler time of the core dump.  For the backtrace one needs
      to read the register state first which can be done from core_pattern
      handler:
      
          ptrace(PTRACE_SEIZE, tid, 0, PTRACE_O_TRACEEXIT)
          close(0);    // close pipe fd to resume the sleeping dumper
          waitpid();   // should report EXIT
          PTRACE_GETREGS or other requests
      
      The remaining problem is how to get the 'tid' value of the crashed
      thread.  It could be read from the first NT_PRSTATUS note of the core
      file but that makes the core_pattern handler complicated.
      
      Unfortunately %t is already used so this patch uses %i/%I.
      
      Automatic Bug Reporting Tool (https://github.com/abrt/abrt/wiki/overview)
      is experimenting with this.  It is using the elfutils
      (https://fedorahosted.org/elfutils/) unwinder for generating the
      backtraces.  Apart from not needing matching executables as mentioned
      above, another advantage is that we can get the backtrace without saving
      the core (which might be quite large) to disk.
      
      [mmilata@redhat.com: final paragraph of changelog]
      Signed-off-by: NJan Kratochvil <jan.kratochvil@redhat.com>
      Signed-off-by: NOleg Nesterov <oleg@redhat.com>
      Cc: Alexander Viro <viro@zeniv.linux.org.uk>
      Cc: Denys Vlasenko <dvlasenk@redhat.com>
      Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
      Cc: Mark Wielaard <mjw@redhat.com>
      Cc: Martin Milata <mmilata@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b03023ec
    • P
      rtc: bq32000: add trickle charger device tree binding · d5fae669
      Pavel Machek 提交于
      BQ32000 have "trickle chargers".  Introduce a device tree binding for
      specifying the trickle charger configuration for that.
      Signed-off-by: NPavel Machek <pavel@denx.de>
      Reviewed-by: NJason Cooper <jason@lakedameon.net>
      Cc: Matti Vaittinen <matti.vaittinen@nsn.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d5fae669