27 Jul, 2006

1 commit


16 Jul, 2006

3 commits


15 Jul, 2006

6 commits

  • Export I/O delays seen by a task through /proc//stats for use in top
    etc.

    Note that delays for I/O done for swapping in pages (swapin I/O) is clubbed
    together with all other I/O here (this is not the case in the netlink
    interface where the swapin I/O is kept distinct)

    [akpm@osdl.org: printk warning fix]
    Signed-off-by: Shailabh Nagar
    Signed-off-by: Balbir Singh
    Cc: Jes Sorensen
    Cc: Peter Chubb
    Cc: Erich Focht
    Cc: Levent Serinol
    Cc: Jay Lan
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Shailabh Nagar
     
  • Documentation for register_chrdev() was missing completely.

    [akpm@osdl.org: kerneldocification]
    Signed-off-by: Rolf Eike Beer
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rolf Eike Beer
     
  • On systems with block devices containing a slash (virtual dasd, cciss,
    etc), reiserfs will fail to initialize /proc/fs/reiserfs/ due to it
    being interpreted as a subdirectory. The generic block device code changes
    the / to ! for use in the sysfs tree. This patch uses that convention.

    Tested by making dm devices use dm/ rather than dm-

    [akpm@osdl.org: name variables consistently]
    Signed-off-by: Jeff Mahoney
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jeff Mahoney
     
  • 2.6.16 leaks like hell. While testing, I found massive leakage
    (reproduced in openvz) in:

    *filp
    *size-4096

    And 1 object leaks in
    *size-32
    *size-64
    *size-128

    It is the fix for the first one. filp leaks in the bowels of namei.c.

    Seems, size-4096 is file table leaking in expand_fdtables.

    I have no idea what are the rest and why they show only accompanying
    another leaks. Some debugging structs?

    [akpm@osdl.org, Trond: remove the IS_ERR() check]
    Signed-off-by: Alexey Kuznetsov
    Cc: Kirill Korotaev
    Cc:
    Cc: Trond Myklebust
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Kirill Korotaev
     
  • Clearign all of i_mode was a bit draconian. We only really care about
    S_ISUID/ISGID, after all.

    Signed-off-by: Linus Torvalds

    Linus Torvalds
     
  • We have a bad interaction with both the kernel and user space being able
    to change some of the /proc file status. This fixes the most obvious
    part of it, but I expect we'll also make it harder for users to modify
    even their "own" files in /proc.

    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

14 Jul, 2006

1 commit


13 Jul, 2006

4 commits

  • We're supposed to go the next power of two if nfds==nr.

    Of `nr', not of `nfsd'.

    Spotted by Rene Scharfe

    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     
  • Address a potential 'larger than buffer size' memory access by
    clear_user(). Without this patch, this call to clear_user() can attempt to
    clear too many (tsz) bytes resulting in a wrong (-EFAULT) return code by
    read_kcore().

    Signed-off-by: Adam B. Jerome
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adam B. Jerome
     
  • sysfs has a different i_mutex lock order behavior for i_mutex than the
    other filesystems; sysfs i_mutex is called in many places with subsystem
    locks held. At the same time, many of the VFS locking rules do not apply
    to sysfs at all (cross directory rename for example). To untangle this
    mess (which gives false positives in lockdep), we're giving sysfs inodes
    their own class for i_mutex.

    Signed-off-by: Arjan van de Ven
    Cc: Ingo Molnar
    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arjan van de Ven
     
  • When found, it is obvious. nfds calculated when allocating fdsets is
    rewritten by calculation of size of fdtable, and when we are unlucky, we
    try to free fdsets of wrong size.

    Found due to OpenVZ resource management (User Beancounters).

    Signed-off-by: Alexey Kuznetsov
    Signed-off-by: Kirill Korotaev
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Kirill Korotaev
     

12 Jul, 2006

1 commit


11 Jul, 2006

12 commits

  • Add an nfs4 operations count array to nfsd_stats structure. The count is
    incremented in nfsd4_proc_compound() where all the operations are handled
    by the nfsv4 server. This count of individual nfsv4 operations is also
    entered into /proc filesystem.

    Signed-off-by: Shankar Anand
    Signed-off-by: Neil Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Shankar Anand
     
  • These functions no longer exist; remove their declarations.

    Signed-off-by: Andreas Gruenbacher
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andreas Gruenbacher
     
  • There's a fairly obvious infinite loop in there.

    Also, use roundup_pow_of_two() rather than open-coding stuff.

    Cc: Eric Dumazet
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     
  • Add coredump capability for the ELF-FDPIC binfmt.

    Signed-off-by: David Howells
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     
  • Move the roundup() macro from binfmt_elf.c into linux/kernel.h as it's
    generally useful.

    [akpm@osdl.org: nuke all the other implementations]
    Signed-off-by: David Howells
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     
  • Adjust the ELF-FDPIC binfmt driver to conform much more to the CodingStyle,
    silly though it may be.

    Further changes:

    (*) Drop the casts to long for addresses in kdebug() statements (they're
    unsigned long already).

    (*) Use extra variables to avoid expressions longer than 80 chars by splitting
    the statement into multiple statements and letting the compiler optimise
    them back together.

    (*) Eliminate duplicate call of ksize() when working out how much space was
    actually allocated for the stack.

    (*) Discard the commented-out load_shlib prototype and op pointer as this will
    not be supported in ELF-FDPIC for the foreseeable future.

    Signed-off-by: David Howells
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     
  • Fix execution through the FDPIC binfmt of programs stored on ramfs by
    preventing the ramfs mmap() returning successfully on a private mapping of
    a ramfs file. This causes NOMMU mmap to make a copy of the mapped portion
    of the file and map that instead.

    This could be improved by granting direct mapping access to read-only
    private mappings for which the data is stored on a contiguous run of pages.
    However, this is only likely to be the case if the file was extended with
    truncate before being written.

    ramfs is left to map the file directly for shared mappings so that SYSV IPC
    and POSIX shared memory both still work.

    Signed-off-by: David Howells
    Cc: Hugh Dickins
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     
  • Fix FDPIC compile errors.

    (akpm: we suspect it fixes a warning)

    Signed-off-by: David Howells
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     
  • Sometimes, applications need below call to be successful although
    "/mnt/hugepages/file1" doesn't exist.

    fd = open("/mnt/hugepages/file1", O_CREAT|O_RDWR, 0755);
    *addr = mmap(NULL, 0x1024*1024*256, PROT_NONE, 0, fd, 0);

    As for regular pages (or files), above call does work, but as for huge
    pages, above call would fail because hugetlbfs_file_mmap would fail if
    (!(vma->vm_flags & VM_WRITE) && len > inode->i_size).

    This capability on huge page is useful on ia64 when the process wants to
    protect one area on region 4, so other threads couldn't read/write this
    area. A famous JVM (Java Virtual Machine) implementation on IA64 needs the
    capability.

    Signed-off-by: Zhang Yanmin
    Cc: David Gibson
    Cc: Hugh Dickins
    [ Expand-on-mmap semantics again... this time matching normal fs's. wli ]
    Acked-by: William Lee Irwin III
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Zhang, Yanmin
     
  • This patch marks an unused export as EXPORT_UNUSED_SYMBOL.

    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian Bunk
     
  • Change the partition code in fs/partitions/check.c to initialize a newly
    detected partition's policy field with that of the containing block device
    (see patch below).

    My reasoning is that function set_disk_ro() in block/genhd.c modifies the
    policy field (read-only indicator) of a disk and all contained partitions.
    When a partition is detected after the call to set_disk_ro(), the policy
    field of this partition will currently not inherit the disk's policy field.
    This behavior poses a problem in cases where a block device can be
    'logically de- and reactivated' like e.g. the s390 DASD driver because
    partition detection may run after the policy field has been modified.

    Signed-off-by: Peter Oberparleiter
    Acked-by: Al Viro
    Makes-sense-to: Jens Axboe
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Peter Oberparleiter
     
  • When write() extends a file(i_size is increased) and fsync() is called,
    change of inode must be written to journaling area through fsync().
    But,currently the i_trans_id is not correctly updated when i_size is
    increased. So fsync() does not kick the journal writer.

    Reiserfs_file_write() already updates the transaction when blocks are
    allocated, but the case when i_size increases and new blocks are not added
    is not correctly treated.

    Following patch fix this bug.

    Signed-off-by: Hisashi Hifumi
    Cc: Jeff Mahoney
    Cc: Chris Mason
    Cc: Hans Reiser
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Hisashi Hifumi
     

10 Jul, 2006

1 commit

  • Several issues noticed/fixed:

    - We cannot reliably block in link_pipe() while holding both input and output
    mutexes. So do preparatory checks before locking down both mutexes and doing
    the link.

    - The ipipe->nrbufs vs i check was bad, because we could have dropped the
    ipipe lock in-between. This causes us to potentially look at unknown
    buffers if we were racing with someone else reading this pipe.

    Signed-off-by: Jens Axboe

    Jens Axboe
     

08 Jul, 2006

1 commit


06 Jul, 2006

9 commits


04 Jul, 2006

1 commit