Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e1fc2b5167f9c3614099e55d3f49763a26a5a339
Commit:     e1fc2b5167f9c3614099e55d3f49763a26a5a339
Parent:     c51d0beaaed902ef48ed1f3b1834d37b7ffd55e8
Author:     Eric Moore <[EMAIL PROTECTED]>
AuthorDate: Sat Sep 29 10:17:49 2007 -0600
Committer:  James Bottomley <[EMAIL PROTECTED]>
CommitDate: Fri Oct 12 14:52:23 2007 -0400

    [SCSI] mptlan: bug fix, only half the message frame is dma'd resulting in 
corruption
    
    NB = number of blocks.  This represents the number of blocks to
    transfer.  The block size is based on the message frame size provided
    in the ioc_facts. A value of zero indicates the entire message frame
    should be copied. This is two bit value.  So by setting this to
    non-zero vaule, you increase performance by reducing amount of data
    needing to be dma'd.  The value that is stored in ioc->ReqeustNB is
    sometimes a non-zero vaule, which creates a bug in mptlan, where not
    the entire message frame is getting transfer to firware, resulting in
    corruption.  This fix sets the default to zero, thus entire message
    frame is copied.
    
    Signed-off-by: Eric Moore <[EMAIL PROTECTED]>
    Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
---
 drivers/message/fusion/mptlan.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/message/fusion/mptlan.c b/drivers/message/fusion/mptlan.c
index b550471..8558322 100644
--- a/drivers/message/fusion/mptlan.c
+++ b/drivers/message/fusion/mptlan.c
@@ -1224,6 +1224,8 @@ mpt_lan_post_receive_buckets(struct mpt_lan_priv *priv)
                }
                pRecvReq = (LANReceivePostRequest_t *) mf;
 
+               i = le16_to_cpu(mf->u.frame.hwhdr.msgctxu.fld.req_idx);
+               mpt_dev->RequestNB[i] = 0;
                count = buckets;
                if (count > max)
                        count = max;
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to