1. 04 4月, 2011 4 次提交
  2. 01 4月, 2011 1 次提交
  3. 31 3月, 2011 3 次提交
  4. 30 3月, 2011 4 次提交
  5. 29 3月, 2011 11 次提交
  6. 28 3月, 2011 12 次提交
  7. 27 3月, 2011 1 次提交
    • O
      NFS: Ensure that rpc_release_resources_task() can be called twice. · a271c5a0
      OGAWA Hirofumi 提交于
      BUG: atomic_dec_and_test(): -1: atomic counter underflow at:
      Pid: 2827, comm: mount.nfs Not tainted 2.6.38 #1
      Call Trace:
       [<ffffffffa02223a0>] ? put_rpccred+0x44/0x14e [sunrpc]
       [<ffffffffa021bbe9>] ? rpc_ping+0x4e/0x58 [sunrpc]
       [<ffffffffa021c4a5>] ? rpc_create+0x481/0x4fc [sunrpc]
       [<ffffffffa022298a>] ? rpcauth_lookup_credcache+0xab/0x22d [sunrpc]
       [<ffffffffa028be8c>] ? nfs_create_rpc_client+0xa6/0xeb [nfs]
       [<ffffffffa028c660>] ? nfs4_set_client+0xc2/0x1f9 [nfs]
       [<ffffffffa028cd3c>] ? nfs4_create_server+0xf2/0x2a6 [nfs]
       [<ffffffffa0295d07>] ? nfs4_remote_mount+0x4e/0x14a [nfs]
       [<ffffffff810dd570>] ? vfs_kern_mount+0x6e/0x133
       [<ffffffffa029605a>] ? nfs_do_root_mount+0x76/0x95 [nfs]
       [<ffffffffa029643d>] ? nfs4_try_mount+0x56/0xaf [nfs]
       [<ffffffffa0297434>] ? nfs_get_sb+0x435/0x73c [nfs]
       [<ffffffff810dd59b>] ? vfs_kern_mount+0x99/0x133
       [<ffffffff810dd693>] ? do_kern_mount+0x48/0xd8
       [<ffffffff810f5b75>] ? do_mount+0x6da/0x741
       [<ffffffff810f5c5f>] ? sys_mount+0x83/0xc0
       [<ffffffff8100293b>] ? system_call_fastpath+0x16/0x1b
      
      Well, so, I think this is real bug of nfs codes somewhere. With some
      review, the code
      
      rpc_call_sync()
          rpc_run_task
              rpc_execute()
                  __rpc_execute()
                      rpc_release_task()
                          rpc_release_resources_task()
                              put_rpccred()                <= release cred
          rpc_put_task
              rpc_do_put_task()
                  rpc_release_resources_task()
                      put_rpccred()                        <= release cred again
      
      seems to be release cred unintendedly.
      Signed-off-by: NOGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      a271c5a0
  8. 26 3月, 2011 1 次提交
  9. 25 3月, 2011 3 次提交
    • D
      ipv4: Fix nexthop caching wrt. scoping. · 37e826c5
      David S. Miller 提交于
      Move the scope value out of the fib alias entries and into fib_info,
      so that we always use the correct scope when recomputing the nexthop
      cached source address.
      Reported-by: NJulian Anastasov <ja@ssi.bg>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      37e826c5
    • D
      ipv4: Invalidate nexthop cache nh_saddr more correctly. · 436c3b66
      David S. Miller 提交于
      Any operation that:
      
      1) Brings up an interface
      2) Adds an IP address to an interface
      3) Deletes an IP address from an interface
      
      can potentially invalidate the nh_saddr value, requiring
      it to be recomputed.
      
      Perform the recomputation lazily using a generation ID.
      Reported-by: NJulian Anastasov <ja@ssi.bg>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      436c3b66
    • T
      Bluetooth: Fix warning with hci_cmd_timer · b77dcf84
      Thomas Gleixner 提交于
      After we made debugobjects working again, we got the following:
      
      WARNING: at lib/debugobjects.c:262 debug_print_object+0x8e/0xb0()
      Hardware name: System Product Name
      ODEBUG: free active (active state 0) object type: timer_list hint: hci_cmd_timer+0x0/0x60
      Pid: 2125, comm: dmsetup Tainted: G        W   2.6.38-06707-gc62b3898 #110375
      Call Trace:
       [<ffffffff8104700a>] warn_slowpath_common+0x7a/0xb0
       [<ffffffff810470b6>] warn_slowpath_fmt+0x46/0x50
       [<ffffffff812d3a5e>] debug_print_object+0x8e/0xb0
       [<ffffffff81bd8810>] ? hci_cmd_timer+0x0/0x60
       [<ffffffff812d4685>] debug_check_no_obj_freed+0x125/0x230
       [<ffffffff810f1063>] ? check_object+0xb3/0x2b0
       [<ffffffff810f3630>] kfree+0x150/0x190
       [<ffffffff81be4d06>] ? bt_host_release+0x16/0x20
       [<ffffffff81be4d06>] bt_host_release+0x16/0x20
       [<ffffffff813a1907>] device_release+0x27/0xa0
       [<ffffffff812c519c>] kobject_release+0x4c/0xa0
       [<ffffffff812c5150>] ? kobject_release+0x0/0xa0
       [<ffffffff812c61f6>] kref_put+0x36/0x70
       [<ffffffff812c4d37>] kobject_put+0x27/0x60
       [<ffffffff813a21f7>] put_device+0x17/0x20
       [<ffffffff81bda4f9>] hci_free_dev+0x29/0x30
       [<ffffffff81928be6>] vhci_release+0x36/0x70
       [<ffffffff810fb366>] fput+0xd6/0x1f0
       [<ffffffff810f8fe6>] filp_close+0x66/0x90
       [<ffffffff810f90a9>] sys_close+0x99/0xf0
       [<ffffffff81d4c96b>] system_call_fastpath+0x16/0x1b
      
      That timer was introduced with commit 6bd32326(Bluetooth: Use
      proper timer for hci command timout)
      
      Timer seems to be running when the thing is closed. Removing the timer
      unconditionally fixes the problem. And yes, it needs to be fixed
      before the HCI_UP check.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Tested-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NGustavo F. Padovan <padovan@profusion.mobi>
      b77dcf84
新手
引导
客服 返回
顶部