linux.git/drivers/nvme, branch v4.12-rc4

nvme: Quirk APST on Intel 600P/P3100 devices

2017-05-26T08:53:02+00:00

They have known firmware bugs.  A fix is apparently in the works --
once fixed firmware is available, someone from Intel (Hi, Keith!)
can adjust the quirk accordingly.

Cc: stable@vger.kernel.org # v4.11
Cc: Kai-Heng Feng 
Cc: Mario Limonciello 
Signed-off-by: Andy Lutomirski 
Signed-off-by: Christoph Hellwig

nvme: only setup block integrity if supported by the driver

2017-05-26T06:54:23+00:00

Currently only the PCIe driver supports metadata, so we should not claim
integrity support for the other drivers.  This prevents nasty crashes
with targets that advertise metadata support on fabrics.

Also use the opportunity to factor out some code into a separate helper
that isn't even compiled if CONFIG_BLK_DEV_INTEGRITY is disabled.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Keith Busch

nvme: replace is_flags field in nvme_ctrl_ops with a flags field

2017-05-26T06:54:16+00:00

So that we can have more flags for transport-specific behavior.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Keith Busch

nvme-pci: consistencly use ctrl->device for logging

2017-05-26T06:54:07+00:00

This is what most of the code already does and gives much more useful
prefixes than the device embedded in the pci_dev.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Keith Busch

nvme_fc: remove extra controller reference taken on reconnect

2017-05-22T18:55:29+00:00

fix extra controller reference taken on reconnect by moving
reference to initial controller create

Signed-off-by: James Smart 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Christoph Hellwig

nvme_fc: correct nvme status set on abort

2017-05-22T18:55:29+00:00

correct nvme status set on abort. Patch that changed status to being actual
nvme status crossed in the night with the patch that added abort values.

Signed-off-by: James Smart 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Christoph Hellwig

nvme_fc: set logging level on resets/deletes

2017-05-22T18:55:29+00:00

Per the review by Sagi on:
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009261.html

Looked at existing warn vs info vs err dev_xxx levels for the messages
printed on reconnects and deletes:
- Resets due to error and resets transitioned to deletes are dev_warn
- Other reset/disconnect messages are dev_info
- Removed chatty io queue related messages

Signed-off-by: James Smart 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Christoph Hellwig

nvme_fc: revise comment on teardown

2017-05-22T18:55:29+00:00

Per the recommendation by Sagi on:
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009261.html

An extra reference was pointed out.  There's no issue with the
references, but rather a literal interpretation of what the comment
is saying.

Reword the comment to avoid confusion.

Signed-off-by: James Smart 
Reviewed-by: Johannes Thumshirn 
Reviewed-by: Hannes Reinecke 
Signed-off-by: Christoph Hellwig

nvme_fc: Support ctrl_loss_tmo

2017-05-22T18:55:29+00:00

Sync with Sagi's recent addition of ctrl_loss_tmo in the core fabrics
layer.

Remove local connect limits and connect_attempts variable.
Use fabrics new nr_connects variable and use of nvmf_should_reconnect()
Refactor duplicate reconnect failure code.

Addresses review comment by Sagi on controller reset support:
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009261.html

Signed-off-by: James Smart 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Christoph Hellwig

nvme_fc: get rid of local reconnect_delay

2017-05-22T18:55:29+00:00

Remove the local copy of reconnect_delay.
Use the value in the controller options directly.

Signed-off-by: James Smart 
Reviewed-by: Hannes Reinecke 
Reviewed-by: Johannes Thumshirn 
Signed-off-by: Christoph Hellwig