netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: wangyunjian <wangyunjian@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	mst@redhat.com, jasowang@redhat.com,
	willemdebruijn.kernel@gmail.com,
	virtualization@lists.linux-foundation.org,
	jerry.lilijun@huawei.com, chenchanghu@huawei.com,
	xudingke@huawei.com, brian.huangbin@huawei.com
Subject: Re: [PATCH net v6] vhost_net: fix ubuf refcount incorrectly when sendmsg fails
Date: Mon, 04 Jan 2021 21:30:08 +0000	[thread overview]
Message-ID: <160979580863.407.3102826648114498407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1609207308-20544-1-git-send-email-wangyunjian@huawei.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Tue, 29 Dec 2020 10:01:48 +0800 you wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
> 
> Currently the vhost_zerocopy_callback() maybe be called to decrease
> the refcount when sendmsg fails in tun. The error handling in vhost
> handle_tx_zerocopy() will try to decrease the same refcount again.
> This is wrong. To fix this issue, we only call vhost_net_ubuf_put()
> when vq->heads[nvq->desc].len == VHOST_DMA_IN_PROGRESS.
> 
> [...]

Here is the summary with links:
  - [net,v6] vhost_net: fix ubuf refcount incorrectly when sendmsg fails
    https://git.kernel.org/netdev/net/c/01e31bea7e62

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-01-04 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29  2:01 [PATCH net v6] vhost_net: fix ubuf refcount incorrectly when sendmsg fails wangyunjian
2021-01-04 21:30 ` patchwork-bot+netdevbpf [this message]

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=160979580863.407.3102826648114498407.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=brian.huangbin@huawei.com \
    --cc=chenchanghu@huawei.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wangyunjian@huawei.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=xudingke@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).