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;
Date:   Wed, 28 Mar 2018 12:01:42 -0700
From:   Stephen Hemminger <stephen@networkplumber.org>
To:     kys@exchange.microsoft.com
Cc:     kys@microsoft.com, gregkh@linuxfoundation.org,
        linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
        olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
        jasowang@redhat.com, leann.ogasawara@canonical.com,
        marcelo.cerri@canonical.com, sthemmin@microsoft.com,
        Michael Kelley <mhkelley@outlook.com>,
        Stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Fix ring buffer signaling
Message-ID: <20180328120142.7ba72aa2@xeon-e3>
In-Reply-To: <20180305052408.19475-1-kys@exchange.microsoft.com>
References: <20180305052408.19475-1-kys@exchange.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun,  4 Mar 2018 22:24:08 -0700
kys@exchange.microsoft.com wrote:

> From: Michael Kelley <mhkelley@outlook.com>
> 
> Fix bugs in signaling the Hyper-V host when freeing space in the
> host->guest ring buffer:
> 
> 1. The interrupt_mask must not be used to determine whether to signal
>    on the host->guest ring buffer
> 2. The ring buffer write_index must be read (via hv_get_bytes_to_write)
>    *after* pending_send_sz is read in order to avoid a race condition
> 3. Comparisons with pending_send_sz must treat the "equals" case as
>    not-enough-space
> 4. Don't signal if the pending_send_sz feature is not present. Older
>    versions of Hyper-V that don't implement this feature will poll.
> 
> Fixes: 03bad714a161 ("vmbus: more host signalling avoidance")
> 
> Cc: Stable <stable@vger.kernel.org> # 4.14 and above
> Signed-off-by: Michael Kelley <mhkelley@outlook.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>

What ever happened to this patch? It doesn't seem to be in char-misc, upstream,
or stable kernel tree yet.