From: patchwork-bot+netdevbpf@kernel.org
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: corbet@lwn.net, willemdebruijn.kernel@gmail.com,
jasowang@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mst@redhat.com,
xuanzhuo@linux.alibaba.com, shuah@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kselftest@vger.kernel.org, yuri.benditovich@daynix.com,
andrew@daynix.com, stephen@networkplumber.org,
gur.stavi@huawei.com, devel@daynix.com, willemb@google.com
Subject: Re: [PATCH net-next v6 0/7] tun: Unify vnet implementation
Date: Tue, 11 Feb 2025 03:30:41 +0000 [thread overview]
Message-ID: <173924464176.3948401.17256177133677367804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250207-tun-v6-0-fb49cf8b103e@daynix.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 07 Feb 2025 15:10:50 +0900 you wrote:
> When I implemented virtio's hash-related features to tun/tap [1],
> I found tun/tap does not fill the entire region reserved for the virtio
> header, leaving some uninitialized hole in the middle of the buffer
> after read()/recvmesg().
>
> This series fills the uninitialized hole. More concretely, the
> num_buffers field will be initialized with 1, and the other fields will
> be inialized with 0. Setting the num_buffers field to 1 is mandated by
> virtio 1.0 [2].
>
> [...]
Here is the summary with links:
- [net-next,v6,1/7] tun: Refactor CONFIG_TUN_VNET_CROSS_LE
https://git.kernel.org/netdev/net-next/c/5a9c5e5d8a1b
- [net-next,v6,2/7] tun: Keep hdr_len in tun_get_user()
https://git.kernel.org/netdev/net-next/c/07e8b3bae2f8
- [net-next,v6,3/7] tun: Decouple vnet from tun_struct
https://git.kernel.org/netdev/net-next/c/60df67b94804
- [net-next,v6,4/7] tun: Decouple vnet handling
https://git.kernel.org/netdev/net-next/c/2506251e81d1
- [net-next,v6,5/7] tun: Extract the vnet handling code
https://git.kernel.org/netdev/net-next/c/1d41e2fa93f7
- [net-next,v6,6/7] tap: Keep hdr_len in tap_get_user()
https://git.kernel.org/netdev/net-next/c/74212f20f366
- [net-next,v6,7/7] tap: Use tun's vnet-related code
https://git.kernel.org/netdev/net-next/c/6a53fc5a8770
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:[~2025-02-11 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 6:10 [PATCH net-next v6 0/7] tun: Unify vnet implementation Akihiko Odaki
2025-02-07 6:10 ` [PATCH net-next v6 1/7] tun: Refactor CONFIG_TUN_VNET_CROSS_LE Akihiko Odaki
2025-02-07 6:10 ` [PATCH net-next v6 2/7] tun: Keep hdr_len in tun_get_user() Akihiko Odaki
2025-02-07 6:10 ` [PATCH net-next v6 3/7] tun: Decouple vnet from tun_struct Akihiko Odaki
2025-02-07 6:10 ` [PATCH net-next v6 4/7] tun: Decouple vnet handling Akihiko Odaki
2025-02-07 6:10 ` [PATCH net-next v6 5/7] tun: Extract the vnet handling code Akihiko Odaki
2025-02-07 17:19 ` Willem de Bruijn
2025-02-07 6:10 ` [PATCH net-next v6 6/7] tap: Keep hdr_len in tap_get_user() Akihiko Odaki
2025-02-07 17:21 ` Willem de Bruijn
2025-02-07 6:10 ` [PATCH net-next v6 7/7] tap: Use tun's vnet-related code Akihiko Odaki
2025-02-11 3: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=173924464176.3948401.17256177133677367804.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akihiko.odaki@daynix.com \
--cc=andrew@daynix.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devel@daynix.com \
--cc=edumazet@google.com \
--cc=gur.stavi@huawei.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuri.benditovich@daynix.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