From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, <netdev@vger.kernel.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH net] xen-netback: fix extra_info handling in xenvif_tx_err()
Date: Thu, 12 May 2016 15:15:33 +0100 [thread overview]
Message-ID: <20160512141533.GL8063@citrix.com> (raw)
In-Reply-To: <1463060583-7524-1-git-send-email-paul.durrant@citrix.com>
On Thu, May 12, 2016 at 02:43:03PM +0100, Paul Durrant wrote:
> Patch 562abd39 "xen-netback: support multiple extra info fragments
> passed from frontend" contained a mistake which can result in an in-
> correct number of responses being generated when handling errors
> encountered when processing packets containing extra info fragments.
> This patch fixes the problem.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Reported-by: Jan Beulich <JBeulich@suse.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
> ---
> drivers/net/xen-netback/netback.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
> index b42f260..4412a57 100644
> --- a/drivers/net/xen-netback/netback.c
> +++ b/drivers/net/xen-netback/netback.c
> @@ -711,6 +711,7 @@ static void xenvif_tx_err(struct xenvif_queue *queue,
> if (cons == end)
> break;
> RING_COPY_REQUEST(&queue->tx, cons++, txp);
> + extra_count = 0; /* only the first frag can have extras */
> } while (1);
> queue->tx.req_cons = cons;
> }
> --
> 2.1.4
>
next prev parent reply other threads:[~2016-05-12 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 13:43 [PATCH net] xen-netback: fix extra_info handling in xenvif_tx_err() Paul Durrant
2016-05-12 14:15 ` Wei Liu [this message]
2016-05-12 14:15 ` Wei Liu
2016-05-13 5:59 ` David Miller
2016-05-13 5:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2016-05-12 13:43 Paul Durrant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160512141533.GL8063@citrix.com \
--to=wei.liu2@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.