From: "Michael S. Tsirkin" <mst@redhat.com>
To: Qin Chuanyu <qinchuanyu@huawei.com>
Cc: davem@davemloft.net, KVM list <kvm@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: orphan frags on local receive
Date: Mon, 24 Feb 2014 15:29:26 +0200 [thread overview]
Message-ID: <20140224132926.GF8981@redhat.com> (raw)
In-Reply-To: <530B4534.3000106@huawei.com>
On Mon, Feb 24, 2014 at 09:12:20PM +0800, Qin Chuanyu wrote:
> with vhost tx zero_copy, guest nic might get hang when host reserving
> skb in socket queue delivered by guest, the case has been solved in
> tun, it also been needed by bridge. This could easily happened when a
> LAST_ACK state tcp occuring between guest and host.
>
> Signed-off-by: Chuanyu Qin <qinchuanyu@huawei.com>
Do you actually observe guest hang?
I would expect orphan frags in
__netif_receive_skb_core to be enough.
> ---
> net/bridge/br_input.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
> index 28d5446..744e27a 100644
> --- a/net/bridge/br_input.c
> +++ b/net/bridge/br_input.c
> @@ -117,6 +117,8 @@ int br_handle_frame_finish(struct sk_buff *skb)
> br->dev->stats.multicast++;
> } else if ((dst = __br_fdb_get(br, dest, vid)) &&
> dst->is_local) {
> + if (unlikely(skb_orphan_frags(skb, GFP_ATOMIC)))
> + goto drop;
> skb2 = skb;
> /* Do not forward the packet since it's local. */
> skb = NULL;
> @@ -136,6 +138,7 @@ int br_handle_frame_finish(struct sk_buff *skb)
> out:
> return 0;
> drop:
> + skb_tx_error(skb);
> kfree_skb(skb);
> goto out;
> }
> --
> 1.7.3.1.msysgit.0
next prev parent reply other threads:[~2014-02-24 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 13:12 [PATCH] bridge: orphan frags on local receive Qin Chuanyu
2014-02-24 13:29 ` Michael S. Tsirkin [this message]
2014-02-24 13:52 ` Qin Chuanyu
2014-02-24 14:31 ` Qin Chuanyu
2014-02-24 15:49 ` Michael S. Tsirkin
2014-02-25 2:02 ` Qin Chuanyu
2014-02-25 3:53 ` Jason Wang
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=20140224132926.GF8981@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qinchuanyu@huawei.com \
/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.