linux-stable.git/drivers/nvme, branch v4.11.2

nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA"

2017-04-20T20:42:10+00:00

There's a report that it malfunctions with APST on.

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

Cc: Kai-Heng Feng 
Signed-off-by: Andy Lutomirski 
Signed-off-by: Jens Axboe

nvme: Adjust the Samsung APST quirk

2017-04-20T20:42:09+00:00

I got a couple more reports: the Samsung APST issues appears to
affect multiple 950-series devices in Dell XPS 15 9550 and Precision
5510 laptops.  Change the quirk: rather than blacklisting the
firmware on the first problematic SSD that was reported, disable
APST on all 144d:a802 devices if they're installed in the two
affected Dell models.  While we're at it, disable only the deepest
sleep state instead of all of them -- the reporters say that this is
sufficient to fix the problem.

(I have a device that appears to be entirely identical to one of the
affected devices, but I have a different Dell laptop, so it's not
the case that all Samsung devices with firmware BXW75D0Q are broken
under all circumstances.)

Samsung engineers have an affected system, and hopefully they'll
give us a better workaround some time soon.  In the mean time, this
should minimize regressions.

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

Cc: Kai-Heng Feng 
Signed-off-by: Andy Lutomirski 
Signed-off-by: Jens Axboe

nvme-fc: Fix sqsize wrong assignment based on ctrl MQES capability

2017-04-09T19:58:11+00:00

both our sqsize and the controller MQES cap are a 0 based value,
so making it 1 based is wrong.

Reported-by: Trapp, Darren 
Reported-by: Daniel Verkamp 
Signed-off-by: Sagi Grimberg 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

nvme-rdma: Fix sqsize wrong assignment based on ctrl MQES capability

2017-04-09T19:58:09+00:00

both our sqsize and the controller MQES cap are a 0 based value,
so making it 1 based is wrong.

Reported-by: Trapp, Darren 
Reported-by: Daniel Verkamp 
Signed-off-by: Sagi Grimberg 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

nvme-loop: Fix sqsize wrong assignment based on ctrl MQES capability

2017-04-09T19:58:07+00:00

both our sqsize and the controller MQES cap are a 0 based value,
so making it 1 based is wrong.

Reported-by: Trapp, Darren 
Reported-by: Daniel Verkamp 
Signed-off-by: Sagi Grimberg 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Jens Axboe

nvmet: fix byte swap in nvmet_parse_io_cmd

2017-04-02T07:24:15+00:00

We need to do arithmetics after byte swapping, not before.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvmet: fix byte swap in nvmet_execute_write_zeroes

2017-04-02T07:24:15+00:00

The length field in the Write Zeroes command is a 16-bit field.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvmet: add missing byte swap in nvmet_get_smart_log

2017-04-02T07:24:15+00:00

In this case entirely harmless as it's all-ones, but still nice to
shut up sparse.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvme: add missing byte swap in nvme_setup_discard

2017-04-02T07:24:15+00:00

Fixes: b35ba01e ("nvme: support ranged discard requests")
Signed-off-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvme-loop: handle cpu unplug when re-establishing the controller

2017-03-21T16:38:46+00:00

If a cpu unplug event has occured, we need to take the minimum
of the provided nr_io_queues and the number of online cpus,
otherwise we won't be able to connect them as blk-mq mapping
won't dispatch to those queues.

Reviewed-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg