[PATCH] storvsc: do not assume SG list is continuous when doing bounce buffers (for 4.1 stable only)

From: Long Li This patch is for linux-stable 4.1 branch only. storvsc checks the SG list for gaps before passing them to Hyper-v device. If there are gaps, data is copied to a bounce buffer and a continuous data buffer is passed to Hyper-V. The check on gaps assumes SG

[PATCHv2 1/2] scsi: Move scsi_cmd->jiffies_at_alloc initialization to allocation time

This second version also sets up jiffies_at_alloc in scsi_init_request. This has been tested without the second patch in the series and I've confirmed I now see the following in the logs after booting: [ 121.718088] sd 1:2:0:0: timing out command, waited 120s [ 121.798081] sd 1:2:1:0: timing

Re: [PATCH 1/2] scsi: Move scsi_cmd->jiffies_at_alloc initialization to allocation time

Scratch this one... Version 2 on the way with the corresponding changes in scsi_init_request... -Brian -- Brian King Power Linux I/O IBM Linux Technology Center

[PATCH 2/2] scsi: Preserve retry counter through scsi_prep_fn

Save / restore the retry counter in scsi_cmd in scsi_init_command. This allows us to go back through scsi_init_command for retries and not forget we are doing a retry. Signed-off-by: Brian King --- Index: linux-2.6.git/drivers/scsi/scsi_lib.c

[PATCH 1/2] scsi: Move scsi_cmd->jiffies_at_alloc initialization to allocation time

Move the initialization of scsi_cmd->jiffies_at_alloc to allocation time rather than prep time. Also ensure that jiffies_at_alloc is preserved when we go through prep. This lets us send retries through prep again and not break the overall retry timer logic in scsi_softirq_done. Suggested-by: Bart

[PATCH 0/2] Allow scsi_prep_fn to occur for retried commands

The following two patches address the hang issue being observed with Bart's patch on powerpc. The first patch moves the initialization of jiffies_at_alloc from scsi_init_command to scsi_init_rq, and ensures we don't zero jiffies_at_alloc in scsi_init_command. The second patch saves / restores the

Re: [PATCH 0/4] constify scsi/tty parisc_device_id

On 19.08.2017 19:54, Arvind Yadav wrote: > parisc_device_id are not supposed to change at runtime. All functions > working with parisc_device_id provided by work with > const parisc_device_id. So mark the non-const structs as const. > > Arvind Yadav (4): > [PATCH 1/4] scsi: lasi700: constify

Re: [PATCH] scsi: sd_zbc: Disable zoned block devices with scsi-mq

Christoph, > But it seems like we need to refne the always unprepare patch first, > to make sure we only release resources, but don't clear the > scmd->retries field. The NVMe driver already works that way, so > we have an example to follow. Agree! -- Martin K. Petersen Oracle Linux

Re: [BUG][bisected 270065e] linux-next fails to boot on powerpc

Brian, >> Thanks for the detailed analysis. This is very helpful. Have you >> considered to change the ipr driver such that it terminates REPORT >> SUPPORTED OPERATION CODES commands with the appropriate check >> condition code instead of DID_ERROR? > > Yes. That data is actually in the sense

Re: [PATCH] ipr: Set no_report_opcodes for RAID arrays

Brian, > Since ipr RAID arrays do not support the MAINTENANCE_IN / > MI_REPORT_SUPPORTED_OPERATION_CODES, set no_report_opcodes to prevent > it from being sent. Applied to 4.13/scsi-fixes. Thank you! -- Martin K. Petersen Oracle Linux Engineering

RE: [PATCH] sd: preserve sysfs updates to max_sectors_kb

> -Original Message- > From: Bart Van Assche [mailto:bart.vanass...@wdc.com] > Sent: Monday, August 21, 2017 2:53 PM > To: h...@infradead.org; Viswas G ; Gerry > Morong ; Mahesh Rajashekhara > ;

Re: [PATCH 06/15] mtd: make device_type const

Le Sat, 19 Aug 2017 13:52:17 +0530, Bhumika Goyal a écrit : > Make this const as it is only stored in the type field of a device > structure, which is const. > Done using Coccinelle. > Applied to l2-mtd/master. Thanks, Boris > Signed-off-by: Bhumika Goyal

Re: [PATCH] sd: preserve sysfs updates to max_sectors_kb

On Mon, 2017-08-21 at 19:12 +, Don Brace wrote: > On Friday Bart Van Assche wrote: > > Can you check on your test system which udev rule changes > > max_sectors_kb? I > > have checked two recent Linux distro's but haven't been able to find > > such a udev rule: > > $ grep -rw max_sectors_kb

RE: [PATCH] sd: preserve sysfs updates to max_sectors_kb

> -Original Message- > From: Bart Van Assche [mailto:bart.vanass...@wdc.com] > Sent: Friday, August 18, 2017 4:47 PM > To: h...@infradead.org; Viswas G ; Gerry > Morong ; Mahesh Rajashekhara > ;

Re: [Regression 4.13-rc1] Resume does not work on Lenovo X60t

Hi Paul, with 4.13-rc6 we're not using blk-mq by default any more, do you still see the issue with that one?

Re: [PATCH] scsi: sd_zbc: Disable zoned block devices with scsi-mq

On Thu, Aug 17, 2017 at 03:01:51PM +, Bart Van Assche wrote: > Another possible approach is to fix the ipr driver and to resubmit the > "scsi-mq: Always unprepare before requeuing a request" and "scsi: sd_zbc: > Write unlock zone from sd_uninit_cmnd()" patches. We should absolutely take that

[PATCH v4 00/14] mpt3sas driver NVMe support:

Ventura Series controller are Tri-mode. The controller and firmware are capable of supporting NVMe devices and PCIe switches to be connected with the controller. This patch set adds driver level support for NVMe devices and PCIe switches. mpt3sas v4 patset: 1) Removed code which detects

[PATCH v4 01/14] mpt3sas: Update MPI Header

From: root Update MPI Files for NVMe support Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S --- drivers/scsi/mpt3sas/mpi/mpi2.h | 43 ++-

[PATCH v4 02/14] mpt3sas: Add nvme device support in slave alloc, target alloc and probe

From: root 1) Added support for probing pcie device and adding NVMe drives to SML and driver's internal list pcie_device_list. 2) Added support for determing NVMe as boot device. 3) Added nvme device support for call back functions scan_finished

[PATCH v4 04/14] mpt3sas: Added support for nvme encapsulated request message.

From: root * Mpt3sas driver uses the NVMe Encapsulated Request message to send an NVMe command to an NVMe device attached to the IOC. * Normal I/O commands like reads and writes are passed to the controller as SCSI commands and the controller has the

[PATCH v4 03/14] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices

From: root * Added support for translating the SGLs associated with incoming commands either to IEE SGL or NVMe PRPs for NVMe devices. * The hardware translation of IEEE SGL to NVMe PRPs has limitation and if a command cannot be translated by

[PATCH v4 05/14] mpt3sas: API 's to support NVMe drive addition to SML

From: root Below Functions are added in various paths to support NVMe drive addition. _scsih_pcie_add_device _scsih_pcie_device_add _scsih_pcie_device_init_add _scsih_check_pcie_access_status _scsih_pcie_check_device mpt3sas_get_pdev_by_handle

[PATCH v4 06/14] mpt3sas: API's to remove nvme drive from sml

From: root Below API's are included in nvme drive remove path. _scsih_pcie_device_remove_by_handle _scsih_pcie_device_remove_from_sml Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S

[PATCH v4 07/14] mpt3sas: Handle NVMe PCIe device related events generated from firmware.

From: root * The controller firmware sends separate events for NVMe devices and PCIe switches similar to existing SAS events. * NVMe device detection, addition and removal are reported by the firmware through PCIe Topology Change list events. * The

[PATCH v4 08/14] mpt3sas: Set NVMe device queue depth as 128

From: root Sets nvme device queue depth, name and displays device capabilities Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S --- drivers/scsi/mpt3sas/mpt3sas_base.h

[PATCH v4 09/14] mpt3sas: scan and add nvme device after controller reset

From: root After Controller reset, Scan and add nvme device back to the topology. Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S Reviewed-by: Hannes Reinecke

[PATCH v4 10/14] mpt3as: Add-Task-management-debug-info-for-NVMe-drives.

From: root Added debug information for NVMe/PCIe drives in target rest path. Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S Reviewed-by: Hannes Reinecke

[PATCH v4 11/14] mpt3sas: NVMe drive support for BTDHMAPPING ioctl command and log info

From: root * Added debug prints for pcie devices in ioctl debug path. Which will be helpful for debugging. * Added PCIe device support for ioctl BTDHMAPPING ioctl. Signed-off-by: Chaitra P B Signed-off-by: Suganath

[PATCH v4 12/14] mpt3sas: Fix nvme drives checking for tlr.

From: root Check for NVMe drives before enabling or checking tlr. Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S Reviewed-by: Hannes Reinecke ---

[PATCH v4 13/14] mpt3sas: Update mpt3sas driver version.

From: root Updated mpt3sas driver version to 15.101.00.00 Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S Reviewed-by: Hannes Reinecke ---

[PATCH v4 14/14] mpt3sas: Fix sparse warning

From: root 1) Used data type __le64/__le32 whichever required in building NVME PRP, which is passed to LE Controller. 2) Remove unused function, Declared functions which are used only in mpt3sas_scsih.c as static. Signed-off-by: Chaitra P B