From: <gregkh@linuxfoundation.org>
To: sagig@mellanox.com, dledford@redhat.com, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "IB/iser: Fix wrong calculation of protection buffer length" has been added to the 3.19-stable tree
Date: Sat, 02 May 2015 19:18:26 +0200 [thread overview]
Message-ID: <143058710611274@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
IB/iser: Fix wrong calculation of protection buffer length
to the 3.19-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ib-iser-fix-wrong-calculation-of-protection-buffer-length.patch
and it can be found in the queue-3.19 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From a065fe6aa25ba6ba93c02dc13486131bb3c64d5f Mon Sep 17 00:00:00 2001
From: Sagi Grimberg <sagig@mellanox.com>
Date: Tue, 14 Apr 2015 18:08:13 +0300
Subject: IB/iser: Fix wrong calculation of protection buffer length
From: Sagi Grimberg <sagig@mellanox.com>
commit a065fe6aa25ba6ba93c02dc13486131bb3c64d5f upstream.
This length miss-calculation may cause a silent data corruption
in the DIX case and cause the device to reference unmapped area.
Fixes: d77e65350f2d ('libiscsi, iser: Adjust data_length to include protection information')
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/infiniband/ulp/iser/iser_initiator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/infiniband/ulp/iser/iser_initiator.c
+++ b/drivers/infiniband/ulp/iser/iser_initiator.c
@@ -409,8 +409,8 @@ int iser_send_command(struct iscsi_conn
if (scsi_prot_sg_count(sc)) {
prot_buf->buf = scsi_prot_sglist(sc);
prot_buf->size = scsi_prot_sg_count(sc);
- prot_buf->data_len = data_buf->data_len >>
- ilog2(sc->device->sector_size) * 8;
+ prot_buf->data_len = (data_buf->data_len >>
+ ilog2(sc->device->sector_size)) * 8;
}
if (hdr->flags & ISCSI_FLAG_CMD_READ) {
Patches currently in stable-queue which might be from sagig@mellanox.com are
queue-3.19/target-file-fix-bug-when-config_debug_sg-y-and-dif-protection-enabled.patch
queue-3.19/ib-core-don-t-disallow-registering-region-starting-at-0x0.patch
queue-3.19/target-file-fix-unmap-with-dif-protection-support.patch
queue-3.19/iser-target-fix-session-hang-in-case-of-an-rdma-read-dif-error.patch
queue-3.19/sd-unregister-integrity-profile.patch
queue-3.19/target-file-fix-sg-table-for-prot_buf-initialization.patch
queue-3.19/iser-target-fix-possible-deadlock-in-rdma_cm-connection-error.patch
queue-3.19/sd-fix-missing-ato-tag-check.patch
queue-3.19/ib-iser-fix-wrong-calculation-of-protection-buffer-length.patch
reply other threads:[~2015-05-02 17:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=143058710611274@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dledford@redhat.com \
--cc=sagig@mellanox.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.