Patch "Drivers: hv: vmbus: Fix ring buffer signaling" has been added to the 4.14-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
Drivers: hv: vmbus: Fix ring buffer signaling
to the 4.14-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:
drivers-hv-vmbus-fix-ring-buffer-signaling.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
655296c8bbeffcf020558c4455305d597a73bde1Mon Sep 17 00:00:00 2001
From: Michael Kelley <[email protected]>
Date: Sun, 4 Mar 2018 22:24:08 -0700
Subject: Drivers: hv: vmbus: Fix ring buffer signaling
From: Michael Kelley <[email protected]>
commit 655296c8bbeffcf020558c4455305d597a73bde1 upstream.
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.
--- drivers/hv/ring_buffer.c | 54 +++++++++++++++++++++++++++++++---------------- 1 file changed, 36 insertions(+), 18 deletions(-)
drivers/hv/ring_buffer.c +36 -18
@@ -394,13 +394,24 @@ __hv_pkt_iter_next(struct vmbus_channel }EXPORT_SYMBOL_GPL (__hv_pkt_iter_next); +/* How many bytes were read in this iterator cycle */ +static u32 hv_pkt_iter_bytes_read (const struct hv_ring_buffer_info *rbi, +u32 start_read_index) +{ +if (rbi->priv_read_index >= start_read_index) +return rbi->priv_read_index - start_read_index; +else +return rbi->ring_datasize - start_read_index + + rbi->priv_read_index; +} +/* * Update host ring buffer after iterating over packets. */ void hv_pkt_iter_close (struct vmbus_channel *channel) {struct hv_ring_buffer_info *rbi = &channel->inbound; -u32 orig_write_sz =hv_get_bytes_to_write (rbi); +u32 curr_write_sz, pending_sz, bytes_read, start_read_index;/* * Make sure all reads are done before we update the read index since
@@ -408,8 +419,12 @@ void hv_pkt_iter_close(struct vmbus_chan* is updated. */ virt_rmb (); + start_read_index = rbi->ring_buffer->read_index; rbi->ring_buffer->read_index = rbi->priv_read_index; +if (!rbi->ring_buffer->feature_bits.feat_pending_send_sz) +return ; +/* * Issue a full memory barrier before making the signaling decision. * Here is the reason for having this barrier:
@@ -423,26 +438,29 @@ void hv_pkt_iter_close(struct vmbus_chan*/ virt_mb (); -/* If host has disabled notifications then skip */ -if (rbi->ring_buffer->interrupt_mask) + pending_sz =READ_ONCE (rbi->ring_buffer->pending_send_sz); +if (!pending_sz)return ; -if (rbi->ring_buffer->feature_bits.feat_pending_send_sz) { -u32 pending_sz =READ_ONCE (rbi->ring_buffer->pending_send_sz); +/* +* Ensure the read of write_index in hv_get_bytes_to_write() +* happens after the read of pending_send_sz. +*/ +virt_rmb (); + curr_write_sz =hv_get_bytes_to_write (rbi); + bytes_read =hv_pkt_iter_bytes_read (rbi, start_read_index); + +/* +* If there was space before we began iteration, +* then host was not blocked. +*/ -/* -* If there was space before we began iteration, -* then host was not blocked. Also handles case where -* pending_sz is zero then host has nothing pending -* and does not need to be signaled. -*/ -if (orig_write_sz > pending_sz) -return ; - -/* If pending write will not fit, don't give false hope. */ -if (hv_get_bytes_to_write (rbi) < pending_sz) -return ; - } +if (curr_write_sz - bytes_read > pending_sz) +return ; + +/* If pending write will not fit, don't give false hope. */ +if (curr_write_sz <= pending_sz) +return ;vmbus_setevent (channel); }
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/drivers-hv-vmbus-fix-ring-buffer-signaling.patch