<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/scsi, branch v4.13-rc4</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi</title>
<updated>2017-08-02T15:43:19+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2017-08-02T15:43:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=33611ba0fed7c7f7768aeb5e0dcda85cc8cf74c4'/>
<id>33611ba0fed7c7f7768aeb5e0dcda85cc8cf74c4</id>
<content type='text'>
Pull SCSI fixes from James Bottomley:
 "These seven patches are mostly minor build, Kconfig and error leg
  fixes"

* tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
  scsi: qedi: Fix return code in qedi_ep_connect()
  scsi: lpfc: fix linking against modular NVMe support
  scsi: scsi_transport_fc: return -EBUSY for deleted vport
  scsi: libcxgbi: add check for valid cxgbi_task_data
  scsi: aic7xxx: fix firmware build with O=path
  scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion
  scsi: qedi: Add ISCSI_BOOT_SYSFS to Kconfig
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull SCSI fixes from James Bottomley:
 "These seven patches are mostly minor build, Kconfig and error leg
  fixes"

* tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
  scsi: qedi: Fix return code in qedi_ep_connect()
  scsi: lpfc: fix linking against modular NVMe support
  scsi: scsi_transport_fc: return -EBUSY for deleted vport
  scsi: libcxgbi: add check for valid cxgbi_task_data
  scsi: aic7xxx: fix firmware build with O=path
  scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion
  scsi: qedi: Add ISCSI_BOOT_SYSFS to Kconfig
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi</title>
<updated>2017-07-26T03:10:10+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2017-07-26T03:10:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=fd2b2c57ec2020ae1b5e24717a876c71e31e5ab8'/>
<id>fd2b2c57ec2020ae1b5e24717a876c71e31e5ab8</id>
<content type='text'>
Pull SCSI fixes from James Bottomley:
 "Three small fixes.

  The transfer size fixes are actually correcting some performance drops
  on the hpsa and smartpqi cards. The cards actually have an internal
  cache for request speed up but bypass it for transfers &gt; 1MB. Since
  4.3 the efficiency of our merges has rendered the cache mostly unused,
  so limit transfers to under 1MB to recover the cache boost"

* tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
  scsi: sg: fix static checker warning in sg_is_valid_dxfer
  scsi: smartpqi: limit transfer length to 1MB
  scsi: hpsa: limit transfer length to 1MB
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Pull SCSI fixes from James Bottomley:
 "Three small fixes.

  The transfer size fixes are actually correcting some performance drops
  on the hpsa and smartpqi cards. The cards actually have an internal
  cache for request speed up but bypass it for transfers &gt; 1MB. Since
  4.3 the efficiency of our merges has rendered the cache mostly unused,
  so limit transfers to under 1MB to recover the cache boost"

* tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
  scsi: sg: fix static checker warning in sg_is_valid_dxfer
  scsi: smartpqi: limit transfer length to 1MB
  scsi: hpsa: limit transfer length to 1MB
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: qedi: Fix return code in qedi_ep_connect()</title>
<updated>2017-07-25T02:24:29+00:00</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2017-07-12T07:31:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=2c67521821acd900d7508f37e49d0b494011106d'/>
<id>2c67521821acd900d7508f37e49d0b494011106d</id>
<content type='text'>
We shouldn't be writing over the "ret" variable.  It means we return
ERR_PTR(0) which is NULL and it results in a NULL dereference in the
caller.

Fixes: ace7f46ba5fd ("scsi: qedi: Add QLogic FastLinQ offload iSCSI driver framework.")
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We shouldn't be writing over the "ret" variable.  It means we return
ERR_PTR(0) which is NULL and it results in a NULL dereference in the
caller.

Fixes: ace7f46ba5fd ("scsi: qedi: Add QLogic FastLinQ offload iSCSI driver framework.")
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: lpfc: fix linking against modular NVMe support</title>
<updated>2017-07-25T02:21:55+00:00</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2017-07-21T20:53:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=cd069bb9f9ff13b23492fda6ccdb458ac4f641ca'/>
<id>cd069bb9f9ff13b23492fda6ccdb458ac4f641ca</id>
<content type='text'>
When LPFC is built-in but NVMe is a loadable module, we fail to link the
kernel:

drivers/scsi/built-in.o: In function `lpfc_nvme_create_localport':
(.text+0x156a82): undefined reference to `nvme_fc_register_localport'
drivers/scsi/built-in.o: In function `lpfc_nvme_destroy_localport':
(.text+0x156eaa): undefined reference to `nvme_fc_unregister_remoteport'

We can avoid this either by forcing lpfc to be a module, or by disabling
NVMe support in this case. This implements the former.

Fixes: 7d7080335f8d ("scsi: lpfc: Finalize Kconfig options for nvme")
Cc: stable@vger.kernel.org
Link: https://patchwork.kernel.org/patch/9636569/
Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When LPFC is built-in but NVMe is a loadable module, we fail to link the
kernel:

drivers/scsi/built-in.o: In function `lpfc_nvme_create_localport':
(.text+0x156a82): undefined reference to `nvme_fc_register_localport'
drivers/scsi/built-in.o: In function `lpfc_nvme_destroy_localport':
(.text+0x156eaa): undefined reference to `nvme_fc_unregister_remoteport'

We can avoid this either by forcing lpfc to be a module, or by disabling
NVMe support in this case. This implements the former.

Fixes: 7d7080335f8d ("scsi: lpfc: Finalize Kconfig options for nvme")
Cc: stable@vger.kernel.org
Link: https://patchwork.kernel.org/patch/9636569/
Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: scsi_transport_fc: return -EBUSY for deleted vport</title>
<updated>2017-07-25T02:17:30+00:00</updated>
<author>
<name>Hannes Reinecke</name>
<email>hare@suse.de</email>
</author>
<published>2017-07-24T10:09:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=260f4aeddb48b16b2f4da306f4d97d44ef102f6b'/>
<id>260f4aeddb48b16b2f4da306f4d97d44ef102f6b</id>
<content type='text'>
When trying to delete a vport via 'vport_delete' sysfs attribute we
should be checking if the port is already in state VPORT_DELETING; if so
there's no need to do anything.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When trying to delete a vport via 'vport_delete' sysfs attribute we
should be checking if the port is already in state VPORT_DELETING; if so
there's no need to do anything.

Signed-off-by: Hannes Reinecke &lt;hare@suse.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: libcxgbi: add check for valid cxgbi_task_data</title>
<updated>2017-07-25T02:16:16+00:00</updated>
<author>
<name>Varun Prakash</name>
<email>varun@chelsio.com</email>
</author>
<published>2017-07-23T14:31:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=5029271072bf55afa6d836180ee93af09b26ab8b'/>
<id>5029271072bf55afa6d836180ee93af09b26ab8b</id>
<content type='text'>
In error case it is possible that -&gt;cleanup_task() gets called without
calling -&gt;alloc_pdu() in this case cxgbi_task_data is not valid, so add
a check for for valid cxgbi_task_data in cxgbi_cleanup_task().

Signed-off-by: Varun Prakash &lt;varun@chelsio.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In error case it is possible that -&gt;cleanup_task() gets called without
calling -&gt;alloc_pdu() in this case cxgbi_task_data is not valid, so add
a check for for valid cxgbi_task_data in cxgbi_cleanup_task().

Signed-off-by: Varun Prakash &lt;varun@chelsio.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: aic7xxx: fix firmware build with O=path</title>
<updated>2017-07-25T02:06:36+00:00</updated>
<author>
<name>Jakub Kicinski</name>
<email>jakub.kicinski@netronome.com</email>
</author>
<published>2017-07-19T01:58:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=516b7db593f3a541e2e98867575c3c697f41a247'/>
<id>516b7db593f3a541e2e98867575c3c697f41a247</id>
<content type='text'>
Building firmware with O=path was apparently broken in aic7 for ever.
Message of the previous commit to the Makefile (from 2008) mentions this
unfortunate state of affairs already.  Fix this, mostly to make
randconfig builds more reliable.

Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Reviewed-by: Hannes Reinecke &lt;hare@suse.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Building firmware with O=path was apparently broken in aic7 for ever.
Message of the previous commit to the Makefile (from 2008) mentions this
unfortunate state of affairs already.  Fix this, mostly to make
randconfig builds more reliable.

Signed-off-by: Jakub Kicinski &lt;jakub.kicinski@netronome.com&gt;
Reviewed-by: Hannes Reinecke &lt;hare@suse.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: megaraid_sas: fix memleak in megasas_alloc_cmdlist_fusion</title>
<updated>2017-07-25T02:06:35+00:00</updated>
<author>
<name>Shu Wang</name>
<email>shuwang@redhat.com</email>
</author>
<published>2017-07-21T10:54:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=70c54e210ee9a2939f39ca58ee0b52afa24addec'/>
<id>70c54e210ee9a2939f39ca58ee0b52afa24addec</id>
<content type='text'>
Found this issue by kmemleak, a few kb mem was leaked in
megasas_alloc_cmdlist_fusion when kzalloc failed for one
megasas_cmd_fusion allocation.

unreferenced object 0xffff88045dbd2000 (size 8192):
  comm "systemd-udevd", pid 323, jiffies 4294671759 (age 49.008s)
  backtrace:
    [&lt;ffffffff8176166a&gt;] kmemleak_alloc+0x4a/0xa0
    [&lt;ffffffff812186a8&gt;] __kmalloc+0xe8/0x220
    [&lt;ffffffffc0060594&gt;] megasas_alloc_cmdlist_fusion+0x34/0xe0 [megaraid_sas]
(gdb) list *megasas_alloc_cmdlist_fusion+0x34
0xd5c4 is in megasas_alloc_cmdlist_fusion
               (drivers/scsi/megaraid/megaraid_sas_fusion.c:443).
    [&lt;ffffffffc0060ca5&gt;] megasas_alloc_cmds_fusion+0x25/0x410 [megaraid_sas]
    [&lt;ffffffffc0061edf&gt;] megasas_init_adapter_fusion+0x21f/0x640 [megaraid_sas]
    [&lt;ffffffffc005df17&gt;] megasas_init_fw+0x357/0xd30 [megaraid_sas]
    [&lt;ffffffffc005ef26&gt;] megasas_probe_one.part.33+0x636/0x1100 [megaraid_sas]
    [&lt;ffffffffc005fa36&gt;] megasas_probe_one+0x46/0xc0 [megaraid_sas]
    [&lt;ffffffff813d2ca5&gt;] local_pci_probe+0x45/0xa0
    [&lt;ffffffff813d4222&gt;] pci_device_probe+0x192/0x1b0
    [&lt;ffffffff814e3658&gt;] driver_probe_device+0x2a8/0x460
    [&lt;ffffffff814e38ed&gt;] __driver_attach+0xdd/0xe0
    [&lt;ffffffff814e124c&gt;] bus_for_each_dev+0x6c/0xc0
    [&lt;ffffffff814e2dde&gt;] driver_attach+0x1e/0x20
    [&lt;ffffffff814e2775&gt;] bus_add_driver+0x45/0x270
    [&lt;ffffffff814e4400&gt;] driver_register+0x60/0xe0
unreferenced object 0xffff880454ce3600 (size 192):
  backtrace:
    [&lt;ffffffff8176166a&gt;] kmemleak_alloc+0x4a/0xa0
    [&lt;ffffffff8121801a&gt;] kmem_cache_alloc_trace+0xca/0x1d0
    [&lt;ffffffffc00605d7&gt;] megasas_alloc_cmdlist_fusion+0x77/0xe0 [megaraid_sas]
(gdb) list *megasas_alloc_cmdlist_fusion+0x77
0xd607 is in megasas_alloc_cmdlist_fusion
                (drivers/scsi/megaraid/megaraid_sas_fusion.c:450).
    [&lt;ffffffffc0060ca5&gt;] megasas_alloc_cmds_fusion+0x25/0x410 [megaraid_sas]
    [&lt;ffffffffc0061edf&gt;] megasas_init_adapter_fusion+0x21f/0x640 [megaraid_sas]
    [&lt;ffffffffc005df17&gt;] megasas_init_fw+0x357/0xd30 [megaraid_sas]
    [&lt;ffffffffc005ef26&gt;] megasas_probe_one.part.33+0x636/0x1100 [megaraid_sas]
    [&lt;ffffffffc005fa36&gt;] megasas_probe_one+0x46/0xc0 [megaraid_sas]
    [&lt;ffffffff813d2ca5&gt;] local_pci_probe+0x45/0xa0
    [&lt;ffffffff813d4222&gt;] pci_device_probe+0x192/0x1b0
    [&lt;ffffffff814e3658&gt;] driver_probe_device+0x2a8/0x460
    [&lt;ffffffff814e38ed&gt;] __driver_attach+0xdd/0xe0
    [&lt;ffffffff814e124c&gt;] bus_for_each_dev+0x6c/0xc0
    [&lt;ffffffff814e2dde&gt;] driver_attach+0x1e/0x20
    [&lt;ffffffff814e2775&gt;] bus_add_driver+0x45/0x270
    [&lt;ffffffff814e4400&gt;] driver_register+0x60/0xe0

Signed-off-by: Shu Wang &lt;shuwang@redhat.com&gt;
Acked-by: Sumit Saxena &lt;sumit.saxena@broadcom.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Found this issue by kmemleak, a few kb mem was leaked in
megasas_alloc_cmdlist_fusion when kzalloc failed for one
megasas_cmd_fusion allocation.

unreferenced object 0xffff88045dbd2000 (size 8192):
  comm "systemd-udevd", pid 323, jiffies 4294671759 (age 49.008s)
  backtrace:
    [&lt;ffffffff8176166a&gt;] kmemleak_alloc+0x4a/0xa0
    [&lt;ffffffff812186a8&gt;] __kmalloc+0xe8/0x220
    [&lt;ffffffffc0060594&gt;] megasas_alloc_cmdlist_fusion+0x34/0xe0 [megaraid_sas]
(gdb) list *megasas_alloc_cmdlist_fusion+0x34
0xd5c4 is in megasas_alloc_cmdlist_fusion
               (drivers/scsi/megaraid/megaraid_sas_fusion.c:443).
    [&lt;ffffffffc0060ca5&gt;] megasas_alloc_cmds_fusion+0x25/0x410 [megaraid_sas]
    [&lt;ffffffffc0061edf&gt;] megasas_init_adapter_fusion+0x21f/0x640 [megaraid_sas]
    [&lt;ffffffffc005df17&gt;] megasas_init_fw+0x357/0xd30 [megaraid_sas]
    [&lt;ffffffffc005ef26&gt;] megasas_probe_one.part.33+0x636/0x1100 [megaraid_sas]
    [&lt;ffffffffc005fa36&gt;] megasas_probe_one+0x46/0xc0 [megaraid_sas]
    [&lt;ffffffff813d2ca5&gt;] local_pci_probe+0x45/0xa0
    [&lt;ffffffff813d4222&gt;] pci_device_probe+0x192/0x1b0
    [&lt;ffffffff814e3658&gt;] driver_probe_device+0x2a8/0x460
    [&lt;ffffffff814e38ed&gt;] __driver_attach+0xdd/0xe0
    [&lt;ffffffff814e124c&gt;] bus_for_each_dev+0x6c/0xc0
    [&lt;ffffffff814e2dde&gt;] driver_attach+0x1e/0x20
    [&lt;ffffffff814e2775&gt;] bus_add_driver+0x45/0x270
    [&lt;ffffffff814e4400&gt;] driver_register+0x60/0xe0
unreferenced object 0xffff880454ce3600 (size 192):
  backtrace:
    [&lt;ffffffff8176166a&gt;] kmemleak_alloc+0x4a/0xa0
    [&lt;ffffffff8121801a&gt;] kmem_cache_alloc_trace+0xca/0x1d0
    [&lt;ffffffffc00605d7&gt;] megasas_alloc_cmdlist_fusion+0x77/0xe0 [megaraid_sas]
(gdb) list *megasas_alloc_cmdlist_fusion+0x77
0xd607 is in megasas_alloc_cmdlist_fusion
                (drivers/scsi/megaraid/megaraid_sas_fusion.c:450).
    [&lt;ffffffffc0060ca5&gt;] megasas_alloc_cmds_fusion+0x25/0x410 [megaraid_sas]
    [&lt;ffffffffc0061edf&gt;] megasas_init_adapter_fusion+0x21f/0x640 [megaraid_sas]
    [&lt;ffffffffc005df17&gt;] megasas_init_fw+0x357/0xd30 [megaraid_sas]
    [&lt;ffffffffc005ef26&gt;] megasas_probe_one.part.33+0x636/0x1100 [megaraid_sas]
    [&lt;ffffffffc005fa36&gt;] megasas_probe_one+0x46/0xc0 [megaraid_sas]
    [&lt;ffffffff813d2ca5&gt;] local_pci_probe+0x45/0xa0
    [&lt;ffffffff813d4222&gt;] pci_device_probe+0x192/0x1b0
    [&lt;ffffffff814e3658&gt;] driver_probe_device+0x2a8/0x460
    [&lt;ffffffff814e38ed&gt;] __driver_attach+0xdd/0xe0
    [&lt;ffffffff814e124c&gt;] bus_for_each_dev+0x6c/0xc0
    [&lt;ffffffff814e2dde&gt;] driver_attach+0x1e/0x20
    [&lt;ffffffff814e2775&gt;] bus_add_driver+0x45/0x270
    [&lt;ffffffff814e4400&gt;] driver_register+0x60/0xe0

Signed-off-by: Shu Wang &lt;shuwang@redhat.com&gt;
Acked-by: Sumit Saxena &lt;sumit.saxena@broadcom.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: qedi: Add ISCSI_BOOT_SYSFS to Kconfig</title>
<updated>2017-07-25T02:06:29+00:00</updated>
<author>
<name>Nilesh Javali</name>
<email>nilesh.javali@cavium.com</email>
</author>
<published>2017-07-19T09:07:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=cc20c29ebc70a227c8bffa46ffc672f81fefa6d7'/>
<id>cc20c29ebc70a227c8bffa46ffc672f81fefa6d7</id>
<content type='text'>
qedi uses iscsi_boot_sysfs to export the targets used for boot to
sysfs. Select the config option to make sure the module is built.

This addresses the compile time issue,
    drivers/scsi/qedi/qedi_main.o: In function `qedi_remove':
    qedi_main.c:(.text+0x3bbd): undefined reference to `iscsi_boot_destroy_kset'
    drivers/scsi/qedi/qedi_main.o: In function `__qedi_probe.constprop.0':
    qedi_main.c:(.text+0x577a): undefined reference to `iscsi_boot_create_target'
    qedi_main.c:(.text+0x5807): undefined reference to `iscsi_boot_create_target'
    qedi_main.c:(.text+0x587f): undefined reference to `iscsi_boot_create_initiator'
    qedi_main.c:(.text+0x58f3): undefined reference to `iscsi_boot_create_ethernet'
    qedi_main.c:(.text+0x5927): undefined reference to `iscsi_boot_destroy_kset'
    qedi_main.c:(.text+0x5d7b): undefined reference to `iscsi_boot_create_host_kset'

[mkp: fixed whitespace]

Signed-off-by: Nilesh Javali &lt;nilesh.javali@cavium.com&gt;
Fixes: c57ec8fb7c02 ("scsi: qedi: Add support for Boot from SAN over iSCSI offload")
Reported-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
qedi uses iscsi_boot_sysfs to export the targets used for boot to
sysfs. Select the config option to make sure the module is built.

This addresses the compile time issue,
    drivers/scsi/qedi/qedi_main.o: In function `qedi_remove':
    qedi_main.c:(.text+0x3bbd): undefined reference to `iscsi_boot_destroy_kset'
    drivers/scsi/qedi/qedi_main.o: In function `__qedi_probe.constprop.0':
    qedi_main.c:(.text+0x577a): undefined reference to `iscsi_boot_create_target'
    qedi_main.c:(.text+0x5807): undefined reference to `iscsi_boot_create_target'
    qedi_main.c:(.text+0x587f): undefined reference to `iscsi_boot_create_initiator'
    qedi_main.c:(.text+0x58f3): undefined reference to `iscsi_boot_create_ethernet'
    qedi_main.c:(.text+0x5927): undefined reference to `iscsi_boot_destroy_kset'
    qedi_main.c:(.text+0x5d7b): undefined reference to `iscsi_boot_create_host_kset'

[mkp: fixed whitespace]

Signed-off-by: Nilesh Javali &lt;nilesh.javali@cavium.com&gt;
Fixes: c57ec8fb7c02 ("scsi: qedi: Add support for Boot from SAN over iSCSI offload")
Reported-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>scsi: sg: fix static checker warning in sg_is_valid_dxfer</title>
<updated>2017-07-18T03:03:48+00:00</updated>
<author>
<name>Johannes Thumshirn</name>
<email>jthumshirn@suse.de</email>
</author>
<published>2017-07-17T13:11:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=14074aba4bcda3764c9a702b276308b89901d5b6'/>
<id>14074aba4bcda3764c9a702b276308b89901d5b6</id>
<content type='text'>
dxfer_len is an unsigned int and we always assign a value &gt; 0 to it, so
it doesn't make any sense to check if it is &lt; 0. We can't really check
dxferp as well as we have both NULL and not NULL cases in the possible
call paths.

So just return true for SG_DXFER_FROM_DEV transfer in
sg_is_valid_dxfer().

Signed-off-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;
Reported-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Cc: Douglas Gilbert &lt;dgilbert@interlog.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
dxfer_len is an unsigned int and we always assign a value &gt; 0 to it, so
it doesn't make any sense to check if it is &lt; 0. We can't really check
dxferp as well as we have both NULL and not NULL cases in the possible
call paths.

So just return true for SG_DXFER_FROM_DEV transfer in
sg_is_valid_dxfer().

Signed-off-by: Johannes Thumshirn &lt;jthumshirn@suse.de&gt;
Reported-by: Colin Ian King &lt;colin.king@canonical.com&gt;
Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Cc: Douglas Gilbert &lt;dgilbert@interlog.com&gt;
Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
