From: patchwork-bot+netdevbpf@kernel.org
To: Cambda Zhu <cambda@linux.alibaba.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, fengtao40@huawei.com,
lucien.xin@gmail.com, luwei32@huawei.com, maheshb@google.com,
xuanzhuo@linux.alibaba.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com
Subject: Re: [PATCH net v2] ipvlan: Fix return value of ipvlan_queue_xmit()
Date: Tue, 27 Jun 2023 10:30:20 +0000 [thread overview]
Message-ID: <168786182007.31138.6869118162868476838.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230626093347.7492-1-cambda@linux.alibaba.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 26 Jun 2023 17:33:47 +0800 you wrote:
> ipvlan_queue_xmit() should return NET_XMIT_XXX, but
> ipvlan_xmit_mode_l2/l3() returns rx_handler_result_t or NET_RX_XXX
> in some cases. ipvlan_rcv_frame() will only return RX_HANDLER_CONSUMED
> in ipvlan_xmit_mode_l2/l3() because 'local' is true. It's equal to
> NET_XMIT_SUCCESS. But dev_forward_skb() can return NET_RX_SUCCESS or
> NET_RX_DROP, and returning NET_RX_DROP(NET_XMIT_DROP) will increase
> both ipvlan and ipvlan->phy_dev drops counter.
>
> [...]
Here is the summary with links:
- [net,v2] ipvlan: Fix return value of ipvlan_queue_xmit()
https://git.kernel.org/netdev/net/c/8a9922e7be6d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-27 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 9:33 [PATCH net v2] ipvlan: Fix return value of ipvlan_queue_xmit() Cambda Zhu
2023-06-27 10: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=168786182007.31138.6869118162868476838.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cambda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=fengtao40@huawei.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=luwei32@huawei.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=xuanzhuo@linux.alibaba.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).