1. 24 9月, 2012 2 次提交
    • S
      [SCSI] zfcp: restore refcount check on port_remove · d99b601b
      Steffen Maier 提交于
      Upstream commit f3450c7b
      "[SCSI] zfcp: Replace local reference counting with common kref"
      accidentally dropped a reference count check before tearing down
      zfcp_ports that are potentially in use by zfcp_units.
      Even remote ports in use can be removed causing
      unreachable garbage objects zfcp_ports with zfcp_units.
      Thus units won't come back even after a manual port_rescan.
      The kref of zfcp_port->dev.kobj is already used by the driver core.
      We cannot re-use it to track the number of zfcp_units.
      Re-introduce our own counter for units per port
      and check on port_remove.
      Signed-off-by: NSteffen Maier <maier@linux.vnet.ibm.com>
      Reviewed-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Cc: <stable@vger.kernel.org> #2.6.33+
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      d99b601b
    • S
      [SCSI] zfcp: Do not wakeup while suspended · cb452149
      Steffen Maier 提交于
      If the mapping of FCP device bus ID and corresponding subchannel
      is modified while the Linux image is suspended, the resume of FCP
      devices can fail. During resume, zfcp gets callbacks from cio regarding
      the modified subchannels but they can be arbitrarily mixed with the
      restore/resume callback. Since the cio callbacks would trigger
      adapter recovery, zfcp could wakeup before the resume callback.
      Therefore, ignore the cio callbacks regarding subchannels while
      being suspended. We can safely do so, since zfcp does not deal itself
      with subchannels. For problem determination purposes, we still trace the
      ignored callback events.
      
      The following kernel messages could be seen on resume:
      
      kernel: <WWPN>: parent <FCP device bus ID> should not be sleeping
      
      As part of adapter reopen recovery, zfcp performs auto port scanning
      which can erroneously try to register new remote ports with
      scsi_transport_fc and the device core code complains about the parent
      (adapter) still sleeping.
      
      kernel: zfcp.3dff9c: <FCP device bus ID>:\
       Setting up the QDIO connection to the FCP adapter failed
      <last kernel message repeated 3 more times>
      kernel: zfcp.574d43: <FCP device bus ID>:\
       ERP cannot recover an error on the FCP device
      
      In such cases, the adapter gave up recovery and remained blocked along
      with its child objects: remote ports and LUNs/scsi devices. Even the
      adapter shutdown as part of giving up recovery failed because the ccw
      device state remained disconnected. Later, the corresponding remote
      ports ran into dev_loss_tmo. As a result, the LUNs were erroneously
      not available again after resume.
      
      Even a manually triggered adapter recovery (e.g. sysfs attribute
      failed, or device offline/online via sysfs) could not recover the
      adapter due to the remaining disconnected state of the corresponding
      ccw device.
      Signed-off-by: NSteffen Maier <maier@linux.vnet.ibm.com>
      Cc: <stable@vger.kernel.org> #2.6.32+
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      cb452149
  2. 20 7月, 2012 1 次提交
    • H
      s390/comments: unify copyright messages and remove file names · a53c8fab
      Heiko Carstens 提交于
      Remove the file name from the comment at top of many files. In most
      cases the file name was wrong anyway, so it's rather pointless.
      
      Also unify the IBM copyright statement. We did have a lot of sightly
      different statements and wanted to change them one after another
      whenever a file gets touched. However that never happened. Instead
      people start to take the old/"wrong" statements to use as a template
      for new files.
      So unify all of them in one go.
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      a53c8fab
  3. 27 8月, 2011 1 次提交
  4. 26 2月, 2011 8 次提交
  5. 17 9月, 2010 3 次提交
  6. 28 7月, 2010 4 次提交
  7. 03 5月, 2010 3 次提交
  8. 18 2月, 2010 4 次提交
  9. 05 12月, 2009 13 次提交
  10. 05 9月, 2009 1 次提交