1. 17 9月, 2010 4 次提交
    • C
      [SCSI] zfcp: Move ACL/CFDC code to zfcp_cfdc.c · a1ca4831
      Christof Schmitt 提交于
      Move the code evaluating the ACL/CFDC specific errors to the file
      zfcp_cfdc.c. With this change, all code related to the old access
      control feature is kept in one file, not split across zfcp_erp.c and
      zfcp_fsf.c.
      Reviewed-by: NSwen Schillig <swen@vnet.ibm.com>
      Signed-off-by: NChristof Schmitt <christof.schmitt@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      a1ca4831
    • C
      [SCSI] zfcp: Reorder FCP I/O and task management handler functions · c61b536c
      Christof Schmitt 提交于
      Instead of calling the same handler for both, I/O and task management
      commands, use different handlers that call a function for the common
      part.
      Reviewed-by: NSwen Schillig <swen@vnet.ibm.com>
      Signed-off-by: NChristof Schmitt <christof.schmitt@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      c61b536c
    • C
      [SCSI] zfcp: Change spin_lock_bh to spin_lock_irq to fix lockdep warning · 44a24cb3
      Christof Schmitt 提交于
      With the change to use the data on the SCSI device, iterating through
      all LUNs/scsi_devices takes the SCSI host_lock. This triggers warnings
      from the lock dependency checker:
      
      =========================================================
      [ INFO: possible irq lock inversion dependency detected ]
      2.6.34.1 #97
      ---------------------------------------------------------
      chchp/3224 just changed the state of lock:
       (&(shost->host_lock)->rlock){-.-...}, at: [<00000000003a73f4>] __scsi_iterate_devices+0x38/0xbc
      but this lock took another, HARDIRQ-unsafe lock in the past:
       (&(&qdio->req_q_lock)->rlock){+.-...}
      
      and interrupts could create inverse lock ordering between them.
      
      other info that might help us debug this: [   24.972394] 2 locks held by chchp/3224:
       #0:  (&(sch->lock)->rlock){-.-...}, at: [<0000000000401efa>] do_IRQ+0xb2/0x1e4
       #1:  (&adapter->port_list_lock){.-....}, at: [<0000000000490302>] zfcp_erp_modify_adapter_status+0x9e/0x16c
      [...]
      
      =========================================================
      [ INFO: possible irq lock inversion dependency detected ]
      2.6.34.1 #98
      ---------------------------------------------------------
      chchp/3235 just changed the state of lock:
       (&(shost->host_lock)->rlock){-.-...}, at: [<00000000003a73f4>] __scsi_iterate_devices+0x38/0xbc
      but this lock took another, HARDIRQ-unsafe lock in the past:
       (&(&qdio->stat_lock)->rlock){+.-...}
      
      and interrupts could create inverse lock ordering between them.
      
      other info that might help us debug this:
      2 locks held by chchp/3235:
       #0:  (&(sch->lock)->rlock){-.-...}, at: [<0000000000401efa>] do_IRQ+0xb2/0x1e4
       #1:  (&adapter->port_list_lock){.-.-..}, at: [<00000000004902f6>] zfcp_erp_modify_adapter_status+0x9e/0x16c
      [...]
      
      To stop this warning, change the request queue lock to disable irqs,
      not only softirq. The changes are required only outside of the
      critical "send fcp command" path.
      Reviewed-by: NSwen Schillig <swen@vnet.ibm.com>
      Signed-off-by: NChristof Schmitt <christof.schmitt@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      44a24cb3
    • C
      [SCSI] zfcp: Use SCSI device data zfcp_scsi_dev instead of zfcp_unit · b62a8d9b
      Christof Schmitt 提交于
      This is the large change to switch from using the data in
      zfcp_unit to zfcp_scsi_dev. Keeping everything working requires doing
      the switch in one piece. To ensure that no code keeps using the data
      in zfcp_unit, this patch also removes the data from zfcp_unit that is
      now being replaced with zfcp_scsi_dev.
      
      For zfcp, the scsi_device together with zfcp_scsi_dev exist from the
      call of slave_alloc to the call of slave_destroy. The data in
      zfcp_scsi_dev is initialized in zfcp_scsi_slave_alloc and the LUN is
      opened; the final shutdown for the LUN is run from slave_destroy.
      
      Where the scsi_device or zfcp_scsi_dev is needed, the pointer to the
      scsi_device is passed as function argument and inside the function
      converted to the pointer to zfcp_scsi_dev; this avoids back and forth
      conversion betweeen scsi_device and zfcp_scsi_dev.
      
      While changing the function arguments from zfcp_unit to scsi_device,
      the functions names are renamed form "unit" to "lun". This is to have
      a seperation between zfcp_scsi_dev/LUN and the zfcp_unit; only code
      referring to the remaining configuration information in zfcp_unit
      struct uses "unit".
      Reviewed-by: NSwen Schillig <swen@vnet.ibm.com>
      Signed-off-by: NChristof Schmitt <christof.schmitt@de.ibm.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@suse.de>
      b62a8d9b
  2. 28 7月, 2010 6 次提交
  3. 22 7月, 2010 3 次提交
  4. 03 5月, 2010 3 次提交
  5. 12 4月, 2010 1 次提交
  6. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  7. 18 2月, 2010 8 次提交
  8. 18 1月, 2010 1 次提交
  9. 05 12月, 2009 11 次提交
  10. 22 10月, 2009 2 次提交