target: Fix reading of data length fields for UNMAP commands
authorRoland Dreier <roland@purestorage.com>
Mon, 16 Jul 2012 22:34:23 +0000 (15:34 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 15 Aug 2012 15:10:31 +0000 (08:10 -0700)
commit6fb6469c601a80a0c883ec0be189ecf1677ecf56
tree7792763b3f2a4025a9a4671659306ec06a63aa41
parent74c90d4c3e5ee158cec2f6f32f6fb3cbfc0a2f47
target: Fix reading of data length fields for UNMAP commands

commit 1a5fa4576ec8a462313c7516b31d7453481ddbe8 upstream.

The UNMAP DATA LENGTH and UNMAP BLOCK DESCRIPTOR DATA LENGTH fields
are in the unmap descriptor (the payload transferred to our data out
buffer), not in the CDB itself.  Read them from the correct place in
target_emulated_unmap.

Signed-off-by: Roland Dreier <roland@purestorage.com>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
[bwh: Backported to 3.2: adjust filename, context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/target/target_core_cdb.c