From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933424AbdC3ID3 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 30 Mar 2017 04:03:29 -0400
Received: from mail.linuxfoundation.org ([140.211.169.12]:42820 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932864AbdC3IDX (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 30 Mar 2017 04:03:23 -0400
Date: Thu, 30 Mar 2017 10:03:06 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: Joseph Salisbury <joseph.salisbury@canonical.com>,
        Long Li <longli@microsoft.com>,
        "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
        "Martin K. Petersen" <martin.petersen@oracle.com>,
        linux-scsi <linux-scsi@vger.kernel.org>,
        Haiyang Zhang <haiyangz@microsoft.com>,
        LKML <linux-kernel@vger.kernel.org>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>,
        "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re:
 [REGRESSION][Stable][v3.12.y][v4.4.y][v4.9.y][v4.10.y][v4.11-rc1] scsi:
 storvsc: properly set residual data length on errors
Message-ID: <20170330080306.GA15809@kroah.com>
References: <5df6cd65-92d5-e4c5-56e3-771643f86861@canonical.com>
 <BLUPR0301MB2098AF08A8AFFC22F2B5D67ACC330@BLUPR0301MB2098.namprd03.prod.outlook.com>
 <f8e619e0-d8b6-bd2f-1a92-c52fbc4b5550@canonical.com>
 <BLUPR0301MB2098105B51A887EEBA6EFD90CC320@BLUPR0301MB2098.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BLUPR0301MB2098105B51A887EEBA6EFD90CC320@BLUPR0301MB2098.namprd03.prod.outlook.com>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Mar 28, 2017 at 04:14:09PM +0000, Stephen Hemminger wrote:
> I decided not to send it to stable since problem was only observed on
> 4.11 but it is probably endemic to all GEN2 VM's

So, what does this mean?  What should stable@ do?  Nothing?  Ok, now
dropped this from my patch queue :)

thanks,

greg k-h