summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorKamlakant Patel <kamlakantp@marvell.com>2019-04-24 14:50:43 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-05-21 19:50:19 +0300
commita01e8a31c837d2670d86610581f3492c0b25d135 (patch)
treee8be318c687460c46292fab81a34b4b442087024 /crypto
parent638ed1824911185bdd531fad546c97a68689b658 (diff)
downloadlinux-a01e8a31c837d2670d86610581f3492c0b25d135.tar.xz
ipmi:ssif: compare block number correctly for multi-part return messages
commit 55be8658c7e2feb11a5b5b33ee031791dbd23a69 upstream. According to ipmi spec, block number is a number that is incremented, starting with 0, for each new block of message data returned using the middle transaction. Here, the 'blocknum' is data[0] which always starts from zero(0) and 'ssif_info->multi_pos' starts from 1. So, we need to add +1 to blocknum while comparing with multi_pos. Fixes: 7d6380cd40f79 ("ipmi:ssif: Fix handling of multi-part return messages"). Reported-by: Kiran Kolukuluru <kirank@ami.com> Signed-off-by: Kamlakant Patel <kamlakantp@marvell.com> Message-Id: <1556106615-18722-1-git-send-email-kamlakantp@marvell.com> [Also added a debug log if the block numbers don't match.] Signed-off-by: Corey Minyard <cminyard@mvista.com> Cc: stable@vger.kernel.org # 4.4 Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions