1. 06 Jan, 2006 1 commit
  2. 30 Sep, 2005 1 commit
  3. 22 Sep, 2005 1 commit
  4. 17 Sep, 2005 2 commits
    • Jeff Dike's avatar
      [PATCH] uml: preserve errno in error paths · b4fd310e
      Jeff Dike authored
      
      
      The poster child for this patch is the third tuntap_user hunk.  When an ioctl
      fails, it properly closes the opened file descriptor and returns.  However,
      the close resets errno to 0, and the 'return errno' that follows returns 0
      rather than the value that ioctl set.  This caused the caller to believe that
      the device open succeeded and had opened file descriptor 0, which caused no
      end of interesting behavior.
      
      The rest of this patch is a pass through the UML sources looking for places
      where errno could be reset before being passed back out.  A common culprit is
      printk, which could call write, being called before errno is returned.
      
      In some cases, where the code ends up being much smaller, I just deleted the
      printk.
      
      There was another case where a caller of run_helper looked at errno after a
      failure, rather than the return value of run_helper, which was the errno value
      that it wanted.
      
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Cc: Paolo Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      b4fd310e
    • Jeff Dike's avatar
      [PATCH] uml: breakpoint an arbitrary thread · 3eddddcf
      Jeff Dike authored
      
      
      This patch implements a stack trace for a thread, not unlike sysrq-t does.
      The advantage to this is that a break point can be placed on showreqs, so that
      upon showing the stack, you jump immediately into the debugger.  While sysrq-t
      does the same thing, sysrq-t shows *all* threads stacks.  It also doesn't work
      right now.  In the future, I thought it might be acceptable to make this show
      all pids stacks, but perhaps leaving well enough alone and just using sysrq-t
      would be okay.  For now, upon receiving the stack command, UML switches
      context to that thread, dumps its registers, and then switches context back to
      the original thread.  Since UML compacts all threads into one of 4 host
      threads, this sort of mechanism could be expanded in the future to include
      other debugging helpers that sysrq does not cover.
      
      Note by jdike - The main benefit to this is that it brings an arbitrary thread
      back into context, where it can be examined by gdb.  The fact that it dumps it
      stack is secondary.  This provides the capability to examine a sleeping
      thread, which has existed in tt mode, but not in skas mode until now.
      
      Also, the other threads, that sysrq doesn't cover, can be gdb-ed directly
      anyway.
      
      Signed-off-by: default avatarAllan <Graves&lt;allan.graves@gmail.com>
      Signed-off-by: default avatarJeff Dike <jdike@addtoit.com>
      Cc: Paolo Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      3eddddcf
  5. 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!
      1da177e4