1. 21 Aug, 2003 1 commit
  2. 20 Aug, 2003 39 commits
    • Linus Torvalds's avatar
    • Linus Torvalds's avatar
      NCR5380: don't play games with NCR5380_proc_info() - just mark it · d4a48a38
      Linus Torvalds authored
      static unconditionally, to allow multiple built-in modules.
      d4a48a38
    • Andrew Morton's avatar
      [PATCH] fix /proc mm_struct refcounting bug · 7d33101c
      Andrew Morton authored
      From: Suparna Bhattacharya <suparna@in.ibm.com>
      
      The /proc code's bare atomic_inc(&mm->count) is racy against __exit_mm()'s
      mmput() on another CPU: it calls mmput() outside task_lock(tsk), and
      task_lock() isn't appropriate locking anyway.
      
      So what happens is:
      
      	CPU0			          CPU1
      
            mmput()
            ->atomic_dec_and_lock(mm->mm_users)
                                                atomic_inc(mm->mm_users)
            ->list_del(mm->mmlist)
                                                mmput()
                                                ->atomic_dec_and_lock(mm->mm_users)
                                                ->list_del(mm->mmlist)
      
      And the double list_del() of course goes splat.
      
      So we use mmlist_lock to synchronise these steps.
      
      The patch implements a new mmgrab() routine which increments mm_users only if
      the mm isn't already going away.  Changes get_task_mm() and proc_pid_stat()
      to call mmgrab() instead of a direct atomic_inc(&mm->mm_users).
      
      Hugh, there's some cruft in swapoff which looks like it should be using
      mmgrab()...
      7d33101c
    • Andrew Morton's avatar
      [PATCH] Fix CPU boot problem · e3e0c299
      Andrew Morton authored
      From: Dave Hansen <haveblue@us.ibm.com>
      
      Hmmm.  This is looking like fallout from the massive wli-bomb.  Here's
      the loop that controls the cpu booting, before and after cpumask_t:
      
      -	for (bit = 0; kicked < NR_CPUS && bit < BITS_PER_LONG; bit++)
      +	for (bit = 0; kicked < NR_CPUS && bit < MAX_APICS; bit++)
      		apicid = cpu_present_to_apicid(bit);
      
      "kicked" only gets incremented for CPUs that were successfully booted,
      so it doesn't help terminate the loop much.  MAX_APICS is 256 on summit,
      which is *MUCH* bigger than BITS_PER_LONG.
      cpu_2_logical_apicid[NR_CPUS] which is referenced from
      cpu_present_to_apicid() is getting referenced up to MAX_APICs, which is
      bigger than NR_CPUS.  Overflow.  Bang.  garbage != BAD_APICID :)
      e3e0c299
    • Andrew Morton's avatar
      [PATCH] missing io_apic.h inclusions · 10d37660
      Andrew Morton authored
      From: Emilio Gallego Arias <egallego@telefonica.net>
      
      Apparently a couple of files now need io_apic.h.
      10d37660
    • Andrew Morton's avatar
      [PATCH] export device_suspend() and device_resume() · 63ee8443
      Andrew Morton authored
      apm.c (at least) needs these.
      63ee8443
    • Andrew Morton's avatar
      [PATCH] fix for htree corruption · b3535b93
      Andrew Morton authored
      From: chrisl@vmware.com
      
      Fixes the "perl installer weirdness" problem which a few people have been
      reporting.
      
      The bug is triggered by creating the index.  Coping out the index we assume
      the dirents start with the first entry after "." "..".
      
      It can make the first previous deleted entry reappear.  In the past we set
      inode to zero for an empty entry so this is not a problem.  That is not
      true any more.
      
      Also, there were a few places where we were altering inode times after
      running ext3_mark_inode_dirty().  We should be doing that beforehand.
      b3535b93
    • Andrew Morton's avatar
      [PATCH] dmi_scan warning fix · 95bc26dc
      Andrew Morton authored
      dmi_dump_system() is only used if CONFIG_ACPI_BOOT.
      95bc26dc
    • Andrew Morton's avatar
      [PATCH] update Documentation/filesystems/Locking · 7f2db912
      Andrew Morton authored
      From: Matthew Wilcox <willy@debian.org>
      
      Here's an update to Documentation/filesystems/Locking.
      7f2db912
    • Andrew Morton's avatar
      [PATCH] fix intel copy_to_user() · 090cd1b4
      Andrew Morton authored
      A `cat /dev/kmem' oopses the kernel.  This is because new Intel
      copy_to_user() doesn't handle segfaults against the kernel-side source
      address of the copy.
      
      It is not obvious how to fix read_kmem(), and handling faults on either
      source or dest is traditional behaviour, so fix it in the copy function by
      adding exception table entries for the reads as well as the writes.
      090cd1b4
    • Andrew Morton's avatar
      [PATCH] dscc4: module refcounting · 895b7792
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      Recent MOD_{INC/DEC}_USE_COUNT removal missed a MOD_DEC_USE_COUNT.
      895b7792
    • Andrew Morton's avatar
      [PATCH] dscc4: various · 1fd793da
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      - silly indentation;
      - let's be more user-friendly with manufacturer specific (mis)feature:
        + s/CONFIG_DSCC4_CLOCK_ON_TWO_PORTS_ONLY/CONFIG_DSCC4_PCISYNC/
        + KConfig adequate entry
      - broken warning message.
      1fd793da
    • Andrew Morton's avatar
      [PATCH] dscc4: CCR1 register fixes · c94a6733
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      CCR1 register voodoo: asic handles itself the flow control.
      c94a6733
    • Andrew Morton's avatar
      [PATCH] dscc4: reset changes · a37a0775
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      Workaround for lack of true reset:
      - devices/ports are put in silent mode at ifconfig down time but some
        state is kept around to allow 'ifconfig up' issuing at a later time.
        Device specific structures are allocated when the pci asic is
        probed: dscc4_init_ring() moves from dscc4_open() to dscc4_found1().
      - try to use reset related board-specific feature at module removal
        time if available. Comments in the code explain the whole story.
        Not a complicated feature but it is unavailable on the cards I own
        and no user gave me feedback -> currently untested.
        It shouldn't harm anyway.
      a37a0775
    • Andrew Morton's avatar
      [PATCH] dscc4: scc changes · 1bcf2af4
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      - more #define for specific bits;
      - more scc_patchl use;
      - just say no to bozo programming:
        + SCC core _really_ disabled at startup;
        + Interrupts Mask Register setup and SCC core activation are
          done as late as possible (i.e. in dscc4_open());
        + they are reverted if dscc4_open() fails;
        + as well as unconditionnaly in dscc4_close();
      - more or less paranoid quirk in Xpr handler.
      1bcf2af4
    • Andrew Morton's avatar
      [PATCH] dscc4: debug messages · 171c33e5
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      More conditional debug messages.
      171c33e5
    • Andrew Morton's avatar
      [PATCH] dscc4: clock mode commentary · b3ddbe8f
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      Clock modes on dscc4 are feature-rich enough to deserve some explanation.
      b3ddbe8f
    • Andrew Morton's avatar
      [PATCH] dscc4: commentary · df527e2e
      Andrew Morton authored
      From: Francois Romieu <romieu@fr.zoreil.com>
      
      Short comments so I can figure why things are done this way.
      df527e2e
    • Andrew Morton's avatar
      [PATCH] opl3sa2 uninitialised spinlock · 0134e16c
      Andrew Morton authored
      opl3sa2 forgot to initialise the spinlock.
      0134e16c
    • Andrew Morton's avatar
      [PATCH] Allow O_EXCL on a block device to claim exclusive use. · c366082d
      Andrew Morton authored
      From: NeilBrown <neilb@cse.unsw.edu.au>
      
      The blockdev layer has a concept of 'claiming' a device, so for example it
      can be claimed when a filesystem is mounted or when it is included into a
      raid array.  Only one subsystem can claim it at a time.
      
      This patch matches this functionality available to user-space via the
      O_EXCL flag to open.
      
      This allows user-space programs to easily test if a device is currently
      mounted etc, and to prevent a device from being mounted or otherwise
      claimed.
      c366082d
    • Andrew Morton's avatar
      [PATCH] When a partition is claimed, claim the whole device · f57dea91
      Andrew Morton authored
      From: NeilBrown <neilb@cse.unsw.edu.au>
      
      Current devices can be 'claimed' by filesystems (when mounting) or
      md/raid (when being included in an array) or 'raw' or ....
      This stop concurrent access by these systems.
      
      However it is still possible for one system to claim the whole device
      and a second system to claim one partition, which is not good.
      
      With this patch, when a partition is claimed, the whole device is 
      claimed for partitioning.  So you cannot have a partition and the
      whole devices claimed at the same time (except if the whole device
      is claimed for partitioning).
      f57dea91
    • Andrew Morton's avatar
      [PATCH] vmscan: give dirty referenced pages another pass · d55158b5
      Andrew Morton authored
      In a further attempt to prevent dirty pages from being written out from the
      LRU, don't write them if they were referenced.  This gives those pages
      another trip around the inactive list.  So more of them are written via
      balance_dirty_pages().
      
      It speeds up an untar-of-five-kernel trees by 5% on a 256M box, presumably
      because balance_dirty_pages() has better IO patterns.
      
      It largely fixes the problem which Gerrit talked about at the kernel summit:
      the individual writepage()s of dirty pages coming off the tail of the LRU are
      reduced by 83% in their database workload.
      
      I'm a bit worried that it increases scanning and OOM possibilities under
      nutty VM stress cases, but nothing untoward has been noted during its four
      weeks in -mm, so...
      d55158b5
    • Andrew Morton's avatar
      [PATCH] ext3 block allocator cleanup · 74d74915
      Andrew Morton authored
      This just reorganizes some ghastly goto-and-retry-spaghetti in the core of
      the ext3 block allocator.
      
      I wrote this ages ago in preparation for fixing the find_next_usable_block()
      CPU pigginess problem, but that proved to be quite nontrivial.
      
      The patch has been in -mm for a long time and Martin has recently confirmed
      that it introduces no performance regression in SDET and kernbench.
      74d74915
    • Andrew Morton's avatar
      [PATCH] misc fixes · 222f1c77
      Andrew Morton authored
      - nmi_watchdog documentation typo ("Randy.Dunlap" <rddunlap@osdl.org>)
      
      - ikconfig proc requires CONFIG_PROC_FS ("Randy.Dunlap" <rddunlap@osdl.org>)
      
      - visws build fix (Andrey Panin <pazke@donpac.ru>)
      
      - VM lock ranking comment update
      222f1c77
    • Linus Torvalds's avatar
      USB serial console: fix compile warning · 3e88b937
      Linus Torvalds authored
      3e88b937
    • Linus Torvalds's avatar
      ultrastor.c: fix bitmap operation type · ee992802
      Linus Torvalds authored
      ee992802
    • Linus Torvalds's avatar
      c1098462
    • Linus Torvalds's avatar
      aacraid: fix "flags" save value. · 4f531b3d
      Linus Torvalds authored
      4f531b3d
    • Linus Torvalds's avatar
    • Jeff Garzik's avatar
      [PATCH] remove mount_root_failed_msg() · df1c4865
      Jeff Garzik authored
      This one snuck in...
      
       - debugging message for ACPI
      
       - Intel guys removed it from their 2.4 tree (at my request)
      
       - it's point-in-time specific (message becomes nearly useless after
         ACPI bug fixes)
      
       - b/c of the point-in-time issue, it's IMO much more appropriate for a
         vendor kernel (where the message, I agree, may be helpful)
      
       - can potentially mislead users to the correct cause of root mount failure
      
       - overall, I disagree with adding messages like this.  The number one
         bug report, by far, for networking drivers is ACPI-related (no
         interrupts delivered).  You don't see me adding "boot with acpi=off"
         messages to the net subsystem.
      df1c4865
    • Jeff Garzik's avatar
      [PATCH] fix ioapic build breakage · f309071a
      Jeff Garzik authored
      f309071a
    • Linus Torvalds's avatar
      net/wan/sbni.c totally misused "pci_request_region()", thinking · e2d8ded1
      Linus Torvalds authored
      it was the same as the old request_region(). Not so.
      e2d8ded1
    • Linus Torvalds's avatar
      Fix smctr.c warning for unused label. · bfd6334f
      Linus Torvalds authored
      bfd6334f
    • Linus Torvalds's avatar
      0ff95582
    • Linus Torvalds's avatar
      6f8d4b06
    • Linus Torvalds's avatar
      Fix video drivers for i2c 'name' move · 783ae816
      Linus Torvalds authored
      783ae816
    • Linus Torvalds's avatar
      Merge home.osdl.org:/home/torvalds/v2.5/zoran · c39d4913
      Linus Torvalds authored
      into home.osdl.org:/home/torvalds/v2.5/linux
      c39d4913
    • Ronald Bultje's avatar
      [PATCH] Big zoran driver update · 4f11c88c
      Ronald Bultje authored
      This is a patch for the video4linux unified zoran driver that has been
      in the kernel since 2.4.5 or so.
      
      It fixes the compile issues in the current 2.6.0-test3 unified zoran
      driver (current one doesn't compile at all), and also updates its
      version to what we have in CVS.  This adds support for new cards (e.g.
      LML33R10 from LinuxMediaLabs and DC30+ from Pinnacle), fixes bugs in
      cards that were already supported and generally improves capture
      reliability.  Changes per file (in detail) are given below. 
      
      i2c-id.h:
        add some new IDs for new i2c drivers
      
      pci_ids.h:
        add PCI IDs for each of the supported cards if it has any
      
      saa7111.c, saa7110.c, adv7175.c, bt819.c, saa7185.c, bt856.c:
        update to whatever we've got in our CVS. For most, these are just
        "easiness" fixes that either add some better debug output, or that make
        maintainance for both 2.6.x and 2.4.x simpler for me. There's also some
        specific changes. E.g., in saa7110.c, we enable the VCR mode bits so we
        get a better image from VCR input. In all of them, we make debugging an
        insmod option rather than a compile-time option (this makes debugging
        for users a *lot* easier). Point is that I just want our latest CVS in
        here. Maintainance is going to be a personal horror-story if it's not.
      
      vpx3220.c, saa7114.c, adv7170.c:
        new i2c ones (for respectively DC10/DC30, LML33R10 and again LML33R10)
      
      zr36067.c:
        removed, the driver is now spread over multiple source files.
      
      zoran*.[ch], zr36057.h
        spread-out source files. Also fixes lots of bugs, can't even start
        naming them all, you don't want that, neither do I. Just assume that it
        works better than it used to - it does.
      
        Nice things that aren't in the old driver: much more stable, supports
        DC30+, supports LML33R10, has proper locking/semaphores, supports
        multiple opens without races now, adapted to new i2c subsystem, v4l2
        support, Xv (hardware-scaled) overlay support, and a lot more.
      
        Oh, and this one actually compiles.
      
      videocodec.[ch], zr360{16,50,60}.[ch]:
        new sublayer for the driver to unify how we handle the zr36060 chip
        (DC10(+)/LML33/LML33R10/Buz) and the zr36050/zr36016 (DC30(+)).
      
      MAINTAINERS:
        add me as maintainer (I am).
      
      Kconfig:
        add new cards, plus improve the descriptions.
      
      Makefile:
        d'oh.
      
      Zoran:
        documentation update.
      
      Others:
        I don't think there are any.
      
      Greg has gone over the i2c changes a long time ago, he agreed on all of
      them. Gerd is supposed to take care of the v4l part, he has never
      complained about any of them. Stability is good, we've fixed most issues
      (there's still some out there, but nothing serious), lots better than in
      the old driver. Also, the cards work much better than with the old
      driver.
      4f11c88c
    • Linus Torvalds's avatar
      Fix up various small compile warnings in an effort at · 51a76834
      Linus Torvalds authored
      getting rid of the simple stuff that hides the serious things. 
      51a76834