1. 15 Apr, 2004 10 commits
    • James Bottomley's avatar
      [PATCH] fix 4k irqstacks on x86 (and add voyager support) · c608aedd
      James Bottomley authored
      There's a bug in the x86 code in that it sets the boot CPU to zero.
      
      This isn't correct since some subarch's use physically indexed CPUs. 
      However, subarchs have either set the boot cpu before irq_INIT() (or
      just inherited the default zero from INIT_THREAD_INFO()), so it's safe
      to believe current_thread_info()->cpu about the boot cpu.
      c608aedd
    • Benjamin Herrenschmidt's avatar
      [PATCH] ppc64: update g5_defconfig · 39d6ca01
      Benjamin Herrenschmidt authored
      This adds IOMMU support & IOMU virtual merging to the default g5 config.
      
      This will not impair performances of machines that don't need the iommu
      (the kernel will only enable it if you have more than 2Gb of RAM, though
      you can explicitely enable it using a command line argument).
      39d6ca01
    • Benjamin Herrenschmidt's avatar
      [PATCH] ppc64: Fix possible duplicate MMU hash entries · cc8a7ced
      Benjamin Herrenschmidt authored
      The current code has a subtle race where 2 hash PTEs can be inserted
      for the same virtual address for a short period of time. There should
      not be a stale one as the "old" one ultimately gets flushed, but the
      architecture specifies that having two hash PTE is illegal and can
      result in undefined behaviour.
      
      This patch fixes it by never clearing the _PAGE_HASHPTE bit when
      doing test_and_clear_{young,dirty}. That means that subsequent faults
      on those pages will have a bit more overhead to "discover" that the
      hash entry was indeed evicted.
      
      It also adds a small optisation to avoid doing the atomic operation
      and the hash flush in test_and_clear_dirty when the page isn't dirty
      or when setting write protect while it's already set.
      cc8a7ced
    • Andrew Morton's avatar
      [PATCH] posix messages queues for s390. · 95c49c77
      Andrew Morton authored
      From: Martin Schwidefsky <schwidefsky@de.ibm.com>
      
      The new message queue interface needs the following patch to get it working
      on s390 (31-bit, 64-bit and 31-bit compat).
      95c49c77
    • Andrew Morton's avatar
      [PATCH] light-weight auditing framework for s390. · 76620e09
      Andrew Morton authored
      From: Martin Schwidefsky <schwidefsky@de.ibm.com>
      
      This patch adds the TIF_SYSCALL_AUDIT option to the s390 ptrace interface.
      76620e09
    • Andrew Morton's avatar
      [PATCH] Add mqueue support to x86-64 · 302be020
      Andrew Morton authored
      From: Andi Kleen <ak@suse.de>
      
      Add POSIX mqueue support to x86-64.
      302be020
    • Andrew Morton's avatar
      [PATCH] ext3: journalled quotas · 2df2c24a
      Andrew Morton authored
      From: Jan Kara <jack@ucw.cz>
      
      Journalled quota support for ext3: The patch consists of two parts - ext3
      changes and changes in generic quota code.  The main idea of the changes is
      that a transaction is always started before any operation which changes quota
      file and dirtifying of the quota causes its write to disk.  These two changes
      assure that quota change is journalled into the same transaction as the file
      change and hence after journal replay quota is consistent with the filesystem
      state.  As during journal replay inodes from orphan list are deleted/truncated
      we have to do quota_on before the replay of the orphan list - this problem is
      solved by additional mount options to ext3 with quota file names and format.
      
      Some changes in generic code were also needed to assure that quota structure
      in file is always allocated and so ordinary quota operations (like
      adding/deleting a block/inode) need only a few blocks from the transaction.
      2df2c24a
    • Andrew Morton's avatar
      [PATCH] mq_open() and close_on_exec · 6ea4e454
      Andrew Morton authored
      From: Chris Wright <chrisw@osdl.org>
      
      SUSv3 doesn't seem to specify one way or the other.  I don't have the POSIX
      specs, and the old docs I have suggest that mq_open() creates an object
      which is to be closed upon exec.
      
      Jakub said:
      
        I think it is valid and required:
      
          http://www.opengroup.org/onlinepubs/007904975/functions/exec.html
      
          All open message queue descriptors in the calling process shall be
          closed, as described in mq_close()
      
        I'll add a new test for this into glibc testsuite.
      6ea4e454
    • Andrew Morton's avatar
      [PATCH] radix-tree comment fix · ae931b63
      Andrew Morton authored
      Fix various bogons and outright lies.
      ae931b63
    • Andrew Morton's avatar
      [PATCH] Fix mq_notify with SIGEV_NONE notification · 4c538514
      Andrew Morton authored
      From: Jakub Jelinek <jakub@redhat.com>
      
      	mq_notify (q, NULL)
      
      and
      	struct sigevent ev = { .sigev_notify = SIGEV_NONE };
      	mq_notify (q, &ev)
      
      are not the same thing in POSIX, yet the kernel treats them the same.  Only
      the former makes the notification available to other processes immediately,
      see
      
      	http://www.opengroup.org/onlinepubs/007904975/functions/mq_notify.html
      
      Without the patch below,
      
      	http://sources.redhat.com/ml/libc-hacker/2004-04/msg00028.html
      
      glibc test fails.
      
      I looked at mq in Solaris and they behave the same in this regard as Linux
      with this patch.  Kernel with this patch passes both Intel POSIX testsuite
      (with testsuite fixes from Ulrich) and glibc mq testsuite.
      4c538514
  2. 14 Apr, 2004 30 commits