Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH] xhci: Add check for invalid byte size error when UAS
 devices are connected.
To:     Sandeep Singh <Sandeep.Singh@amd.com>,
        linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
        gregkh@linuxfoundation.org, mathias.nyman@intel.com
Cc:     Nehal Shah <Nehal-bakulchandra.Shah@amd.com>,
        Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
References: <1537536150-11721-1-git-send-email-Sandeep.Singh@amd.com>
From:   Mathias Nyman <mathias.nyman@linux.intel.com>
Message-ID: <58201720-ee34-a866-b177-084b9f36c40c@linux.intel.com>
Date:   Mon, 24 Sep 2018 16:09:59 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <1537536150-11721-1-git-send-email-Sandeep.Singh@amd.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 21.09.2018 16:22, Sandeep Singh wrote:
> From: Sandeep Singh <sandeep.singh@amd.com>
> 
> Observed "TRB completion code (27)" error which corresponds to Stopped -
> Length Invalid error(xhci spec section 4.17.4) while connecting USB to
> SATA bridge.
> 
> Looks like this case was not considered when the following patch[1] was
> committed. Hence adding this new check which can prevent
> the invalid byte size error.
> 
> [1] ade2e3a xhci: handle transfer events without TRB pointer
> 

Thanks, adding to queue.

Just out of curiosity, was the TRB pointer bits all zeroes
in this  Stopped -Length invalid transfer event TRB?

-Mathias