1. 20 8月, 2008 10 次提交
    • L
      vfat: fix 'sync' mount deadlock due to BKL->lock_super conversion · 5f22ca9b
      Linus Torvalds 提交于
      There was another FAT BKL conversion deadlock reported by Bart
      Trojanowski due to the BKL being used as a recursive lock by FAT, which
      was missed because it only triggers with 'sync' (or 'dirsync') mounts.
      
      The recursion worked for the BKL, but after the conversion to lock_super
      (which uses a mutex), it just deadlocks.
      
      Thanks to Bart for debugging this and testing the fix.  The lock
      debugging information from the original report:
      
        =============================================
        [ INFO: possible recursive locking detected ]
        2.6.27-rc3-bisect-00448-ga7f5aaf3 #16
        ---------------------------------------------
        mv/4020 is trying to acquire lock:
         (&type->s_lock_key#9){--..}, at: [<c01a90fe>] lock_super+0x1e/0x20
      
        but task is already holding lock:
         (&type->s_lock_key#9){--..}, at: [<c01a90fe>] lock_super+0x1e/0x20
      
        other info that might help us debug this:
        3 locks held by mv/4020:
         #0:  (&sb->s_type->i_mutex_key#9/1){--..}, at: [<c01b2336>] do_unlinkat+0x66/0x140
         #1:  (&sb->s_type->i_mutex_key#9){--..}, at: [<c01b0954>] vfs_unlink+0x84/0x110
         #2:  (&type->s_lock_key#9){--..}, at: [<c01a90fe>] lock_super+0x1e/0x20
      
        stack backtrace:
        Pid: 4020, comm: mv Not tainted 2.6.27-rc3-bisect-00448-ga7f5aaf3 #16
         [<c014e694>] validate_chain+0x984/0xea0
         [<c0108d70>] ? native_sched_clock+0x0/0xf0
         [<c014ee9c>] __lock_acquire+0x2ec/0x9b0
         [<c014f5cf>] lock_acquire+0x6f/0x90
         [<c01a90fe>] ? lock_super+0x1e/0x20
         [<c044e5fd>] mutex_lock_nested+0xad/0x300
         [<c01a90fe>] ? lock_super+0x1e/0x20
         [<c01a90fe>] ? lock_super+0x1e/0x20
         [<c01a90fe>] lock_super+0x1e/0x20
         [<f8b3a700>] fat_write_inode+0x60/0x2b0 [fat]
         [<c0450878>] ? _spin_unlock_irqrestore+0x48/0x80
         [<f8b3a953>] ? fat_sync_inode+0x3/0x20 [fat]
         [<f8b3a962>] fat_sync_inode+0x12/0x20 [fat]
         [<f8b37c7e>] fat_remove_entries+0xbe/0x120 [fat]
         [<f8b422ef>] vfat_unlink+0x5f/0x90 [vfat]
         [<f8b42290>] ? vfat_unlink+0x0/0x90 [vfat]
         [<c01b0968>] vfs_unlink+0x98/0x110
         [<c01b2400>] do_unlinkat+0x130/0x140
         [<c016a8f5>] ? audit_syscall_entry+0x105/0x150
         [<c01b253b>] sys_unlinkat+0x3b/0x40
         [<c01040d3>] sysenter_do_call+0x12/0x3f
         =======================
      
      where the deadlock is due to the nesting of lock_super from vfat_unlink
      to fat_write_inode:
      
       - do_unlinkat
         - vfs_unlink
           - vfat_unlink
             * lock_super
             - fat_remove_entries
               - fat_sync_inode
                 - fat_write_inode
                   * lock_super
      
      and the fix is to simply remove the use of lock_super() in fat_write_inode.
      
      The lock_super() there had been just an automatic conversion of the
      kernel lock to the superblock lock, but no locking was actually needed
      there, since the code in fat_write_inode already protected all relevant
      accesses with a spinlock (sbi->inode_hash_lock to be exact).  The only
      code inside the BKL (and thus the superblock lock) was accesses tp local
      variables or calls to functions that have long been SMP-safe (i.e.
      sb_bread, mark_buffe_dirty and brlese).
      
      Bart reports:
       "Looks good.  I ran 10 parallel processes creating 1M files truncating
        them, writing to them again and then deleting them.  This patch fixes
        the issue I ran into.
      
        Signed-off-by: Bart Trojanowski <bart@jukie.net>"
      Reported-and-tested-by: NBart Trojanowski <bart@jukie.net>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      5f22ca9b
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6 · 395c6846
      Linus Torvalds 提交于
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6:
        firewire: Kconfig help update
        ieee1394: sbp2: let nodemgr retry node updates during bus reset series
        ieee1394: don't drop nodes during bus reset series
        ieee1394: regression in 2.6.25: updates should happen before probes
      395c6846
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 · ddd13dc6
      Linus Torvalds 提交于
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6:
        PCI: add acpi_find_root_bridge_handle
        PCI: acpi_pcihp: run _OSC on a root bridge
        x86/PCI: irq and pci_ids patch for Intel Ibex Peak PCHs
        x86/PCI: allow scanning of 255 PCI busses
        x86, pci: detect end_bus_number according to acpi/e820 reserved, v2
        pci: debug extra pci bus resources
        pci: debug extra pci resources range
      ddd13dc6
    • L
      Revert "[CPUFREQ][2/2] preregister support for powernow-k8" · f607e3a0
      Linus Torvalds 提交于
      This reverts commit 34ae7f35, which has
      been reported to cause a number of problems.  During suspend and resume,
      it apparently causes a crash in a CPU hotplug notifier to happen,
      although the exact details are sketchy because of the inability to get
      good traces during the suspend sequence.
      
      See buzilla entries
      
      	http://bugzilla.kernel.org/show_bug.cgi?id=11296
      	http://bugzilla.kernel.org/show_bug.cgi?id=11339
      
      for more examples and details.
      
      [ Mark: "Revert the patch for now.  I'm still looking into getting a
        reliable reproduction and I do not have a fix at this time." ]
      Requested-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NMark Langsdorf <mark.langsdorf@amd.com>
      Acked-by: NDave Jones <davej@redhat.com>
      Signed-off-by: NLinus Torvalds <torvalds@inux-foundation.org>
      f607e3a0
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input · 96d6d72d
      Linus Torvalds 提交于
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
        Input: evdev - fix printf() format for sizeof
        Input: remove version.h from drivers that don't need it
        Input: cobalt_btns - add missing MODULE_LICENSE
      96d6d72d
    • L
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6 · 4309e092
      Linus Torvalds 提交于
      * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: (94 commits)
        pkt_sched: Prevent livelock in TX queue running.
        Revert "pkt_sched: Add BH protection for qdisc_stab_lock."
        Revert "pkt_sched: Protect gen estimators under est_lock."
        pkt_sched: remove bogus block (cleanup)
        nf_nat: use secure_ipv4_port_ephemeral() for NAT port randomization
        netfilter: ctnetlink: sleepable allocation with spin lock bh
        netfilter: ctnetlink: fix sleep in read-side lock section
        netfilter: ctnetlink: fix double helper assignation for NAT'ed conntracks
        netfilter: ipt_addrtype: Fix matching of inverted destination address type
        dccp: Fix panic caused by too early termination of retransmission mechanism
        pkt_sched: Don't hold qdisc lock over qdisc_destroy().
        pkt_sched: Add lockdep annotation for qdisc locks
        pkt_sched: Never schedule non-root qdiscs.
        removed unused #include <version.h>
        rt2x00: Fix txdone_entry_desc_flags
        b43: Fix for another Bluetooth Coexistence SPROM Programming error for BCM4306
        mac80211: remove kdoc references to IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE
        p54u: reset skb's data/tail pointer on requeue
        p54: move p54_vdcf_init to the right place.
        iwlwifi: fix printk newlines
        ...
      4309e092
    • S
      firewire: Kconfig help update · 30b0aa7c
      Stefan Richter 提交于
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      30b0aa7c
    • S
      ieee1394: sbp2: let nodemgr retry node updates during bus reset series · a3384067
      Stefan Richter 提交于
      sbp2 was too quick to report .update() to the ieee1394 core as failed.
      (Logged as "Failed to reconnect to sbp2 device!".)  The core would then
      unbind sbp2 from the device.
      
      This is not justified if the .update() failed because another bus reset
      happened.  We check this and tell the ieee1394 that .update() succeeded,
      and the core will call sbp2's .update() for the new bus reset as well.
      
      This improves reconnection/re-login especially on buses with several
      disks as they may issue bus resets in close succession when they come
      online.
      
      Tested by Damien Benoist.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      a3384067
    • S
      ieee1394: don't drop nodes during bus reset series · c921a974
      Stefan Richter 提交于
      nodemgr_node_probe checked for generation increments too late and
      therefore prematurely reported nodes as "suspended".
      
      Fixes http://bugzilla.kernel.org/show_bug.cgi?id=11349.  Reported and
      tested by Damien Benoist.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      c921a974
    • S
      ieee1394: regression in 2.6.25: updates should happen before probes · 6848408a
      Stefan Richter 提交于
      Regression since commit 73cf6023,
      "ieee1394: use class iteration api":  The two loops for (1.) driver
      updates and (2.) driver probes were replaced by a single loop with
      bogus needs_probe checks.  Hence updates and probes were now intermixed,
      and especially sbp2 updates (reconnects) held up longer than necessary.
      
      While we fix it, change the needs_probe flag to bool type for clarity.
      
      Tested by Damien Benoist.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      6848408a
  2. 19 8月, 2008 30 次提交