1. 26 7月, 2011 4 次提交
  2. 23 7月, 2011 1 次提交
  3. 21 7月, 2011 1 次提交
  4. 28 6月, 2011 1 次提交
  5. 27 5月, 2011 1 次提交
  6. 25 5月, 2011 11 次提交
  7. 24 5月, 2011 1 次提交
  8. 18 5月, 2011 1 次提交
  9. 29 4月, 2011 3 次提交
  10. 15 4月, 2011 2 次提交
  11. 14 4月, 2011 1 次提交
  12. 10 4月, 2011 1 次提交
  13. 31 3月, 2011 1 次提交
  14. 30 3月, 2011 1 次提交
  15. 25 3月, 2011 3 次提交
    • T
      um: Use generic show_interrupts() · df31a0a0
      Thomas Gleixner 提交于
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      df31a0a0
    • T
      um: Convert genirq namespace · 0ebec35f
      Thomas Gleixner 提交于
      Scripted with coccinelle.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      0ebec35f
    • T
      percpu: Always align percpu output section to PAGE_SIZE · 0415b00d
      Tejun Heo 提交于
      Percpu allocator honors alignment request upto PAGE_SIZE and both the
      percpu addresses in the percpu address space and the translated kernel
      addresses should be aligned accordingly.  The calculation of the
      former depends on the alignment of percpu output section in the kernel
      image.
      
      The linker script macros PERCPU_VADDR() and PERCPU() are used to
      define this output section and the latter takes @align parameter.
      Several architectures are using @align smaller than PAGE_SIZE breaking
      percpu memory alignment.
      
      This patch removes @align parameter from PERCPU(), renames it to
      PERCPU_SECTION() and makes it always align to PAGE_SIZE.  While at it,
      add PCPU_SETUP_BUG_ON() checks such that alignment problems are
      reliably detected and remove percpu alignment comment recently added
      in workqueue.c as the condition would trigger BUG way before reaching
      there.
      
      For um, this patch raises the alignment of percpu area.  As the area
      is in .init, there shouldn't be any noticeable difference.
      
      This problem was discovered by David Howells while debugging boot
      failure on mn10300.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NMike Frysinger <vapier@gentoo.org>
      Cc: uclinux-dist-devel@blackfin.uclinux.org
      Cc: David Howells <dhowells@redhat.com>
      Cc: Jeff Dike <jdike@addtoit.com>
      Cc: user-mode-linux-devel@lists.sourceforge.net
      0415b00d
  16. 23 3月, 2011 3 次提交
    • R
      um: remove file pointer from ioctl · 8a06dc4d
      Richard Weinberger 提交于
      Commit 6caa76b7 ("tty: now phase out the ioctl file pointer for good")
      removed the ioctl file pointer.  User Mode Linux's line driver uses this
      ioctl and needs a signature update too.
      Signed-off-by: NRichard Weinberger <richard@nod.at>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Greg KH <greg@kroah.com>
      Cc: Jeff Dike <jdike@addtoit.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8a06dc4d
    • P
      uml: kernels on {i386,x86_64} produce bad coredumps · 13e165ba
      Paul Pluzhnikov 提交于
      One of our users reported that when a user-level program SIGSEGVs under
      UML kernel, the resulting core dump is not very usable.
      
      I have reproduced that with the latest kernel:
      
        make ARCH=um defconfig; make ARCH=um
      
      Run the resulting kernel, then "inside" run this program:
      
      #include <pthread.h>
      
      void *fn(void *p)
      {
       abort();
      }
      
      int main()
      {
       pthread_t tid;
       pthread_create(&tid, 0, fn, 0);
       pthread_join(tid, 0);
       return 0;
      }
      
      Analyze the coredump with GDB. Here is what you'll see:
      
      sudo gdb -q -ex 'set solib-absolute-prefix ../root_fs' -ex 'file ../root_fs/var/tmp/mt-abort' -ex 'core ../root_fs/var/tmp/core.762'
      Reading symbols from /usr/local/google/root_fs/var/tmp/mt-abort...done.
      [New Thread 763]
      [New Thread 762]
      Core was generated by `./mt-abort'.
      Program terminated with signal 6, Aborted.
      #0  0x0000000040255250 in raise () from ../root_fs/lib64/libc.so.6
      (gdb) info thread
        2 Thread 762  0x0000000000000000 in ?? ()
      * 1 Thread 763  0x0000000040255250 in raise () from ../root_fs/lib64/libc.so.6
      
      Note that thread#2 looks funny.
      
      (gdb) thread 2
      [Switching to thread 2 (Thread 762)]#0  0x0000000000000000 in ?? ()
      (gdb) info reg
      rax            0x0      0
      rbx            0x0      0
      rcx            0x0      0
      rdx            0x0      0
      rsi            0x0      0
      rdi            0x0      0
      rbp            0x0      0x0
      rsp            0x0      0x0
      r8             0x0      0
      r9             0x0      0
      r10            0x0      0
      r11            0x0      0
      r12            0x0      0
      r13            0x0      0
      r14            0x0      0
      r15            0x0      0
      rip            0x0      0
      eflags         0x0      [ ]
      cs             0x0      0
      ss             0x0      0
      ds             0x0      0
      es             0x0      0
      fs             0x0      0
      gs             0x0      0
      
      Examining the core shows that NT_PRSTATUS notes for all threads other than
      the one that crashed are zeroed out.
      
      I believe this is happening because neither ELF_CORE_COPY_TASK_REGS nor
      task_pt_regs are defined under ARCH=um, and so elf_core_copy_task_regs()
      becomes a no-op.
      
      Attached patch fixes this for SUBARCH={x86_64,i386}.
      Signed-off-by: NPaul Pluzhnikov <ppluzhnikov@google.com>
      Cc: Jeff Dike <jdike@addtoit.com>
      Acked-by: NWANG Cong <xiyou.wangcong@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      13e165ba
    • E
      mm: NUMA aware alloc_task_struct_node() · 504f52b5
      Eric Dumazet 提交于
      All kthreads being created from a single helper task, they all use memory
      from a single node for their kernel stack and task struct.
      
      This patch suite creates kthread_create_on_cpu(), adding a 'cpu' parameter
      to parameters already used by kthread_create().
      
      This parameter serves in allocating memory for the new kthread on its
      memory node if available.
      
      Users of this new function are : ksoftirqd, kworker, migration, pktgend...
      
      This patch:
      
      Add a node parameter to alloc_task_struct(), and change its name to
      alloc_task_struct_node()
      
      This change is needed to allow NUMA aware kthread_create_on_cpu()
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      Reviewed-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NRusty Russell <rusty@rustcorp.com.au>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: David Howells <dhowells@redhat.com>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      504f52b5
  17. 17 3月, 2011 1 次提交
  18. 14 3月, 2011 1 次提交
    • A
      open-style analog of vfs_path_lookup() · 73d049a4
      Al Viro 提交于
      new function: file_open_root(dentry, mnt, name, flags) opens the file
      vfs_path_lookup would arrive to.
      
      Note that name can be empty; in that case the usual requirement that
      dentry should be a directory is lifted.
      
      open-coded equivalents switched to it, may_open() got down exactly
      one caller and became static.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      73d049a4
  19. 09 3月, 2011 1 次提交
  20. 01 3月, 2011 1 次提交