1. 25 7月, 2017 1 次提交
  2. 27 6月, 2017 1 次提交
  3. 16 5月, 2017 1 次提交
    • M
      scsi: fix some kernel-doc markups · 739aca06
      Mauro Carvalho Chehab 提交于
      Sphinx is very pedantic with regards to ident/spacing.
      Fix some kernel-doc markups in order to solve those
      errors/warnings:
      
      ./drivers/scsi/scsicam.c:121: WARNING: Inline emphasis start-string without end-string.
      ./drivers/scsi/scsicam.c:121: WARNING: Inline emphasis start-string without end-string.
      ./drivers/scsi/scsicam.c:121: WARNING: Inline emphasis start-string without end-string.
      ./drivers/scsi/scsi_scan.c:1056: ERROR: Unexpected indentation.
      ./drivers/scsi/scsi_scan.c:1057: WARNING: Block quote ends without a blank line; unexpected unindent.
      ./drivers/scsi/scsi_transport_fc.c:2918: ERROR: Unexpected indentation.
      ./drivers/scsi/scsi_transport_fc.c:2921: WARNING: Block quote ends without a blank line; unexpected unindent.
      ./drivers/scsi/scsi_transport_fc.c:2922: WARNING: Enumerated list ends without a blank line; unexpected unindent.
      
      No functional changes.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      739aca06
  4. 20 4月, 2017 1 次提交
  5. 19 4月, 2017 1 次提交
  6. 07 2月, 2017 2 次提交
  7. 28 1月, 2017 2 次提交
  8. 18 11月, 2016 12 次提交
  9. 15 11月, 2016 1 次提交
  10. 09 11月, 2016 1 次提交
  11. 12 4月, 2016 2 次提交
  12. 01 12月, 2015 1 次提交
  13. 10 4月, 2015 1 次提交
  14. 26 7月, 2014 1 次提交
  15. 18 7月, 2014 2 次提交
  16. 25 6月, 2014 1 次提交
    • N
      fc: ensure scan_work isn't active when freeing fc_rport · 0353e085
      Neil Horman 提交于
      debugfs caught this:
      WARNING: at lib/debugobjects.c:260 debug_print_object+0x83/0xa0()
      ODEBUG: free active (active state 0) object type: work_struct
      hint: fc_scsi_scan_rport+0x0/0xd0 [scsi_transport_fc]
       CPU: 1 PID: 184 Comm: kworker/1:1 Tainted: G        W
      --------------   3.10.0-123.el7.x86_64.debug #1
      Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013
      Workqueue: fc_wq_5 fc_rport_final_delete [scsi_transport_fc]
      Call Trace:
      [<ffffffff8169efec>] dump_stack+0x19/0x1b
      [<ffffffff8106cbd1>] warn_slowpath_common+0x61/0x80
      [<ffffffff8106cc4c>] warn_slowpath_fmt+0x5c/0x80
      [<ffffffff8133e003>] debug_print_object+0x83/0xa0
      [<ffffffffa04e2f40>] ? fc_parse_wwn+0x100/0x100
      
      [<ffffffff8133f23b>] debug_check_no_obj_freed+0x22b/0x270
      [<ffffffffa04e127e>] ? fc_rport_dev_release+0x1e/0x30
      [<ffffffff811db3e9>] kfree+0xd9/0x2d0
      [<ffffffffa04e127e>] fc_rport_dev_release+0x1e/0x30
      [<ffffffff81428032>] device_release+0x32/0xa0
      [<ffffffff8132701e>] kobject_release+0x7e/0x1b0
      [<ffffffff81326ed8>] kobject_put+0x28/0x60
      [<ffffffff81428397>] put_device+0x17/0x20
      [<ffffffffa04e5025>] fc_rport_final_delete+0x165/0x210
      [<ffffffff810959b0>] process_one_work+0x220/0x710
      [<ffffffff81095944>] ? process_one_work+0x1b4/0x710
      [<ffffffff81095fbb>] worker_thread+0x11b/0x3a0
      [<ffffffff81095ea0>] ? process_one_work+0x710/0x710
      [<ffffffff8109e0cd>] kthread+0xed/0x100
      [<ffffffff8109dfe0>] ? insert_kthread_work+0x80/0x80
      [<ffffffff816b2fec>] ret_from_fork+0x7c/0xb0
      [<ffffffff8109dfe0>] ? insert_kthread_work+0x80/0x80
      
      Seems to be because the scan_work work_struct might be active when the housing
      fc_rport struct gets freed.  Ensure that we cancel it prior to freeing the rport
      Signed-off-by: NNeil Horman <nhorman@tuxdriver.com>
      Reviewed-by: NVasu Dev <vasu.dev@intel.com>
      Reviewed-by: NHannes Reinecke <hare@suse.de>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      0353e085
  17. 16 3月, 2014 1 次提交
  18. 04 7月, 2013 1 次提交
  19. 29 3月, 2013 1 次提交
  20. 20 7月, 2012 2 次提交
  21. 25 6月, 2012 1 次提交
    • T
      block: drop custom queue draining used by scsi_transport_{iscsi|fc} · 86072d81
      Tejun Heo 提交于
      iscsi_remove_host() uses bsg_remove_queue() which implements custom
      queue draining.  fc_bsg_remove() open-codes mostly identical logic.
      
      The draining logic isn't correct in that blk_stop_queue() doesn't
      prevent new requests from being queued - it just stops processing, so
      nothing prevents new requests to be queued after the logic determines
      that the queue is drained.
      
      blk_cleanup_queue() now implements proper queue draining and these
      custom draining logics aren't necessary.  Drop them and use
      bsg_unregister_queue() + blk_cleanup_queue() instead.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Reviewed-by: NMike Christie <michaelc@cs.wisc.edu>
      Acked-by: NVivek Goyal <vgoyal@redhat.com>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: James Smart <james.smart@emulex.com>
      Signed-off-by: NJens Axboe <axboe@kernel.dk>
      86072d81
  22. 10 5月, 2012 1 次提交
  23. 19 2月, 2012 1 次提交
  24. 16 1月, 2012 1 次提交
    • J
      [SCSI] scsi_transport_fc: Clear Devloss Callback Done flag in fc_remote_port_rolechg · 0eecee41
      James Smart 提交于
      This patch fixes a bug where devloss is not called on fc_host teardown.
      The issue is seen if the LLDD uses rport_rolechg to add the target role
      to an rport.
      
      When an rport goes away, the LLDD will call fc_remote_port_delete, which
      will start the devloss timer.  If the timer expires, the transport will
      call the devloss callback and set the FC_RPORT_DEVLOSS_CALLBK_DONE flag.
      However, the rport structure is not deleted, it is retained to store the
      SCSI id mappings for the rport in case it comes back. In the scenario
      where it does come back, and the driver calls fc_remote_port_add, but does
      not indicate the "target" role for the rport - the create will clear the
      structure, but forgets to clear FC_RPORT_DEVLOSS_CALLBK_DONE flag (which
      is cleared if it's added with the target role). The secondary call, of
      fc_remote_port_rolechg to add the target role also does not clear the flag.
      Thus, the next time the rport goes away, the resulting devloss timer
      expiration will not call the driver callback as the flag is still set.
      
      This patch adds the FC_RPORT_DEVLOSS_CALLBK_DONE flags to the list of
      those that are cleared upon reuse of the rport structure.
      Signed-off-by: NAlex Iannicelli <alex.iannicelli@emulex.com>
      Signed-off-by: NJames Smart <james.smart@emulex.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      0eecee41