1. 17 9月, 2014 1 次提交
    • R
      scsi: use 'depends' instead of 'select' for SCSI_FC_ATTRS · 6a38792c
      Randy Dunlap 提交于
      There are other kconfig symbols which use SCSI_FC_ATTRS.
      In order to maintain sanity and prevent kconfig warnings, change
      all of these from using 'select' to using 'depends on' so that
      proper symbol dependencies will be honored and circular depends
      problems will be avoided.
      This fixes kconfig warnings and build errors:
      
      warning: (LIBFC && SCSI_IBMVFC && SCSI_QLA_FC && SCSI_LPFC && ZFCP && SCSI_BFA_FC && SCSI_CHELSIO_FCOE && FUSION_FC) selects SCSI_FC_ATTRS which has unmet direct dependencies (SCSI && NET)
      drivers/scsi/scsi_transport_fc.c: In function 'fc_host_post_event':
      drivers/scsi/scsi_transport_fc.c:543:7: error: 'scsi_nl_sock' undeclared (first use in this function)
      drivers/scsi/scsi_transport_fc.c: In function 'fc_host_post_vendor_event':
      drivers/scsi/scsi_transport_fc.c:611:7: error: 'scsi_nl_sock' undeclared (first use in this function)
      
      Reported-by: Fengguang Wu <fengguang.wu@intel.com> [0-day test robot]
      Signed-off-by: NRandy Dunlap <rdunlap@infradead.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a38792c
  2. 16 9月, 2014 2 次提交
  3. 26 7月, 2014 2 次提交
  4. 18 7月, 2014 4 次提交
  5. 03 6月, 2014 1 次提交
    • N
      virtio-scsi: Enable DIF/DIX modes in SCSI host LLD · e6dc783a
      Nicholas Bellinger 提交于
      This patch updates virtscsi_probe() to setup necessary Scsi_Host
      level protection resources. (currently hardcoded to 1)
      
      It changes virtscsi_add_cmd() to attach outgoing / incoming
      protection SGLs preceeding the data payload, and is using the
      new virtio_scsi_cmd_req_pi->pi_bytes[out,in] field to signal
      to signal to vhost/scsi bytes to expect for protection data.
      
      (Add missing #include <linux/blkdev.h> for blk_integrity - sfr + nab)
      Acked-by: NPaolo Bonzini <pbonzini@redhat.com>
      Cc: Michael S. Tsirkin <mst@redhat.com>
      Cc: Martin K. Petersen <martin.petersen@oracle.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Hannes Reinecke <hare@suse.de>
      Cc: Sagi Grimberg <sagig@dev.mellanox.co.il>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Signed-off-by: NNicholas Bellinger <nab@linux-iscsi.org>
      e6dc783a
  6. 11 4月, 2014 1 次提交
    • D
      scsi: async sd resume · 3c31b52f
      Dan Williams 提交于
      async_schedule() sd resume work to allow disks and other devices to
      resume in parallel.
      
      This moves the entirety of scsi_device resume to an async context to
      ensure that scsi_device_resume() remains ordered with respect to the
      completion of the start/stop command.  For the duration of the resume,
      new command submissions (that do not originate from the scsi-core) will
      be deferred (BLKPREP_DEFER).
      
      It adds a new ASYNC_DOMAIN_EXCLUSIVE(scsi_sd_pm_domain) as a container
      of these operations.  Like scsi_sd_probe_domain it is flushed at
      sd_remove() time to ensure async ops do not continue past the
      end-of-life of the sdev.  The implementation explicitly refrains from
      reusing scsi_sd_probe_domain directly for this purpose as it is flushed
      at the end of dpm_resume(), potentially defeating some of the benefit.
      Given sdevs are quiesced it is permissible for these resume operations
      to bleed past the async_synchronize_full() calls made by the driver
      core.
      
      We defer the resolution of which pm callback to call until
      scsi_dev_type_{suspend|resume} time and guarantee that the callback
      parameter is never NULL.  With this in place the type of resume
      operation is encoded in the async function identifier.
      
      There is a concern that async resume could trigger PSU overload.  In the
      enterprise, storage enclosures enforce staggered spin-up regardless of
      what the kernel does making async scanning safe by default.  Outside of
      that context a user can disable asynchronous scanning via a kernel
      command line or CONFIG_SCSI_SCAN_ASYNC.  Honor that setting when
      deciding whether to do resume asynchronously.
      
      Inspired by Todd's analysis and initial proposal [2]:
      https://01.org/suspendresume/blogs/tebrandt/2013/hard-disk-resume-optimization-simpler-approach
      
      Cc: Len Brown <len.brown@intel.com>
      Cc: Phillip Susi <psusi@ubuntu.com>
      [alan: bug fix and clean up suggestion]
      Acked-by: NAlan Stern <stern@rowland.harvard.edu>
      Suggested-by: NTodd Brandt <todd.e.brandt@linux.intel.com>
      [djbw: kick all resume work to the async queue]
      Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      3c31b52f
  7. 19 12月, 2013 1 次提交
    • P
      [SCSI] aci7xxx_old: delete decade+ obsolete driver · 1a4049dd
      Paul Gortmaker 提交于
      After getting warnings in an allyesconfig build[1] from this
      driver, I decided to remind myself just how old it was, and
      whether it warranted fixing.  In the Kconfig help text, I found:
      
        "This driver will eventually be phased out entirely"
      
      Going back to the history archive, I see the line was added[2]
      in Feb 2002, when we moved from v2.4.2.1 ---> v2.4.2.2
      
      So, with over a decade of notification, and multiple major releases
      since then, I think we can justify removing this.  Currently we have
      people wasting time building it during routine testing, and then
      wasting more time re-researching the known reported warnings, only to
      find that nobody really is willing to integrate the fixes[3] for it.
      
      A quick search didn't seem to indicate any active user base for it.
      If someone happens to have a quirky _old_ card that the eleven year
      old "new" driver doesn't work with, then it is entirely reasonable
      that they stick with a kernel version that predates this removal.
      
      [1] drivers/scsi/aic7xxx_old.c: In function ‘aic7xxx_register’:
          drivers/scsi/aic7xxx_old.c:7901:5: warning: case value ‘257’ not in enumerated type ‘ahc_chip’ [-Wswitch]
          drivers/scsi/aic7xxx_old.c:7898:5: warning: case value ‘513’ not in enumerated type ‘ahc_chip’ [-Wswitch]
          drivers/scsi/aic7xxx_old.c: In function ‘aic7xxx_load_seeprom’:
          drivers/scsi/aic7xxx_old.c:8517:5: warning: case value ‘257’ not in enumerated type ‘ahc_chip’ [-Wswitch]
          drivers/scsi/aic7xxx_old.c:8510:5: warning: case value ‘513’ not in enumerated type ‘ahc_chip’ [-Wswitch]
      
      [2] http://git.kernel.org/cgit/linux/kernel/git/tglx/history.git commit 44e8778c
      
      [3] https://lkml.org/lkml/2012/10/29/215Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Acked-by: NHannes Reinecke <hare@suse.de>
      Acked-by: NDoug Ledford <dledford@redhat.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      1a4049dd
  8. 02 12月, 2013 1 次提交
  9. 03 9月, 2013 1 次提交
  10. 22 8月, 2013 1 次提交
    • A
      [SCSI] lpfc: Don't force CONFIG_GENERIC_CSUM on · f5944daa
      Anton Blanchard 提交于
      We want ppc64 to be able to select between optimised assembly
      checksum routines in big endian and the generic lib/checksum.c
      routines in little endian.
      
      The lpfc driver is forcing CONFIG_GENERIC_CSUM on which means
      we are unable to make the decision to enable it in the arch
      Kconfig. If the option exists it is always forced on.
      
      This got introduced in 3.10 via commit 6a7252fd ([SCSI] lpfc:
      fix up Kconfig dependencies). I spoke to Randy about it and
      the original issue was with CRC_T10DIF not being defined.
      
      As such, remove the select of CONFIG_GENERIC_CSUM.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Cc: <stable@vger.kernel.org> # 3.10
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      f5944daa
  11. 27 6月, 2013 1 次提交
  12. 10 5月, 2013 1 次提交
  13. 22 1月, 2013 1 次提交
  14. 09 1月, 2013 1 次提交
  15. 01 12月, 2012 1 次提交
  16. 27 11月, 2012 1 次提交
  17. 20 7月, 2012 2 次提交
    • A
      [SCSI] aha152x: Allow use on 64bit systems · fa7250d6
      Alan Cox 提交于
      This is reported to work, known to work on PCMCIA and a code check shows no
      problems on the other bits of the code.
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      fa7250d6
    • J
      [SCSI] Remove scsi_wait_scan module · 6072609d
      James Bottomley 提交于
      scsi_wait_scan was introduced with asynchronous host scanning as a hack
      for distributions that weren't using proper udev based wait for root to
      appear in their initramfs scripts.  In 2.6.30 Commit
      
      c7510859
      Author: Rafael J. Wysocki <rjw@sisk.pl>
      Date:   Sun Apr 12 20:06:56 2009 +0200
      
          PM/Hibernate: Wait for SCSI devices scan to complete during resume
      
      Actually broke scsi_wait_scan because it renders
      scsi_complete_async_scans() a nop for modular SCSI if you include
      scsi_scans.h (which this module does).
      
      The lack of bug reports is sufficient proof that this module is no
      longer used.
      
      Cc: Jeff Mahoney <jeffm@suse.de>
      Cc: Dave Jones <davej@redhat.com>
      Cc: maximilian attems <max@stro.at>
      Signed-off-by: NJames Bottomley <JBottomley@Parallels.com>
      6072609d
  18. 18 5月, 2012 1 次提交
    • P
      scsi: delete the MCA specific drivers and driver code · a88dc06c
      Paul Gortmaker 提交于
      The support for CONFIG_MCA is being removed, since the 20
      year old hardware simply isn't capable of meeting today's
      software demands on CPU and memory resources.
      
      This commit removes the MCA specific SCSI drivers, and the
      MCA specific portions of code in dual role ISA/MCA drivers.
      Also, the MCA specific SCSI documentation is removed.
      
      Cc: James Bottomley <JBottomley@parallels.com>
      Cc: linux-scsi@vger.kernel.org
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      a88dc06c
  19. 24 4月, 2012 1 次提交
  20. 27 3月, 2012 1 次提交
  21. 09 3月, 2012 1 次提交
  22. 19 2月, 2012 1 次提交
  23. 14 2月, 2012 1 次提交
  24. 16 1月, 2012 1 次提交
  25. 01 11月, 2011 1 次提交
  26. 24 9月, 2011 1 次提交
  27. 27 8月, 2011 3 次提交
  28. 03 7月, 2011 3 次提交
  29. 01 3月, 2011 1 次提交
  30. 18 10月, 2010 1 次提交