27 Jul, 2007

4 commits


25 Jul, 2007

3 commits

  • kunmap_atomic() takes the virtual address, not the mapped page as
    argument.

    Signed-off-by: Jens Axboe
    Cc: Mark Fasheh
    Signed-off-by: Linus Torvalds

    Jens Axboe
     
  • * 'request-queue-t' of git://git.kernel.dk/linux-2.6-block:
    [BLOCK] Add request_queue_t and mark it deprecated
    [BLOCK] Get rid of request_queue_t typedef

    Linus Torvalds
     
  • The fallocate syscall returns ENOSYS in case the filesystem does not support
    the operation and expects the userlevel code to fill in. This is good in
    concept.

    The problem is that the libc code for old kernels should be able to
    distinguish the case where the syscall is not at all available vs not
    functioning for a specific mount point. As is this is not possible and we
    always have to invoke the syscall even if the kernel doesn't support it.

    I suggest the following patch. Using EOPNOTSUPP is IMO the right thing to do.

    Cc: Amit Arora
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ulrich Drepper
     

24 Jul, 2007

1 commit

  • Some of the code has been gradually transitioned to using the proper
    struct request_queue, but there's lots left. So do a full sweet of
    the kernel and get rid of this typedef and replace its uses with
    the proper type.

    Signed-off-by: Jens Axboe

    Jens Axboe
     

23 Jul, 2007

1 commit


22 Jul, 2007

5 commits

  • Too many remote cpu references due to /proc/stat.

    On x86_64, with newer kernel versions, kstat_irqs is a bit of a problem.
    On every call to kstat_irqs, the process brings in per-cpu data from all
    online cpus. Doing this for NR_IRQS, which is now 256 + 32 * NR_CPUS
    results in (256+32*63) * 63 remote cpu references on a 64 cpu config.
    /proc/stat is parsed by common commands like top, who etc, causing lots
    of cacheline transfers

    This statistic seems useless. Other 'big iron' arches disable this.

    AK: changed to remove for all SMP setups
    AK: add comment

    Signed-off-by: Ravikiran Thirumalai
    Signed-off-by: Andi Kleen
    Signed-off-by: Linus Torvalds

    Ravikiran G Thirumalai
     
  • There are reports of this causing userspace failures
    (http://lkml.org/lkml/2007/7/20/421).

    Revert.

    Cc: Jan Kratochvil
    Cc: Jiri Kosina
    Cc: Ingo Molnar
    Cc: Roland McGrath
    Cc: Jakub Jelinek
    Cc: Ulrich Kunitz
    Cc: "H. Peter Anvin"
    Cc: "Bret Towe"
    Cc: "Luck, Tony"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     
  • For display purposes, treat uid's and gid's as unsigned ints for now.
    Also fix a typo.

    Signed-off-by: "J. Bruce Fields"
    Cc: Neil Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    J. Bruce Fields
     
  • This is an variation on the patch sent by Christoph Hellwig which kills
    file_count abuse by the Coda kernel module by moving the coda_flush
    functionality into coda_release. However part of reason we were using the
    coda_flush callback was to allow Coda to pass errors that occur during
    writeback from the userspace cache manager back to close().

    As Al Viro explained on linux-fsdevel, it is impossible to guarantee that
    such errors can in fact be returned back to the caller. There are many
    cases where the last reference to a file is not released by the close
    system call and it is also impossible to pick some close as a 'last-close'
    and delay it until all other references have been destroyed.

    The CODA_STORE/CODA_RELEASE upcall combination is clearly a broken design,
    and it is better to remove it completely.

    Signed-off-by: Jan Harkes
    Cc: Christoph Hellwig
    Cc: Al Viro
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jan Harkes
     
  • This patch fixes up sources after conversion by Lindent.

    Signed-off-by: Cyrill Gorcunov
    Cc: Jan Kara
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Cyrill Gorcunov
     

21 Jul, 2007

1 commit

  • If add_to_page_cache_lru() fails, the page will not be locked. But
    splice jumps to an error path that does a page release and unlock,
    causing a BUG() in unlock_page().

    Fix this by adding one more label that just releases the page. This bug
    was actually triggered on EL5 by gurudas pai
    using fio.

    Signed-off-by: Jens Axboe
    Signed-off-by: Linus Torvalds

    Jens Axboe
     

20 Jul, 2007

25 commits