diff options
| author |   Jakub Kicinski <kuba@kernel.org> | 2025-02-10 19:07:13 -0800 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2025-02-10 19:07:13 -0800 |
| commit | 51b2483b087c8a26c085a2870a0651fea1712785 (patch) | |
| tree | 7a8797255890a61b03a6225f798509cf65c309be /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Merge branch 'net-xilinx-axienet-enable-adaptive-irq-coalescing-with-dim' (diff) | |
| parent | tap: Use tun's vnet-related code (diff) | |
| download | linux-rng-51b2483b087c8a26c085a2870a0651fea1712785.tar.xz linux-rng-51b2483b087c8a26c085a2870a0651fea1712785.zip | |
Merge branch 'tun-unify-vnet-implementation'
Akihiko Odaki says:
====================
tun: Unify vnet implementation
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].
The change to virtio header is preceded by another change that refactors
tun and tap to unify their virtio-related code.
[1]: https://lore.kernel.org/r/20241008-rss-v5-0-f3cf68df005d@daynix.com
[2]: https://lore.kernel.org/r/20241227084256-mutt-send-email-mst@kernel.org/
====================
Link: https://patch.msgid.link/20250207-tun-v6-0-fb49cf8b103e@daynix.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions