linux-kernel - Re: [PATCH net-next v7 2/2] virtio-net: Implement ndo_write_rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPrAcgOp6K_udUQUZhb+JhJqS26M3YjBzHDdS=i1_9iXy+3k7A@mail.gmail.com>
Date: Wed, 7 Jan 2026 11:42:45 +0530
From: I Viswanath <viswanathiyyappan@...il.com>
To: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>
Cc: netdev@...r.kernel.org, virtualization@...ts.linux.dev, 
	linux-kernel@...r.kernel.org, edumazet@...gle.com, andrew+netdev@...n.ch, 
	horms@...nel.org, kuba@...nel.org, pabeni@...hat.com, mst@...hat.com, 
	eperezma@...hat.com, jasowang@...hat.com
Subject: Re: [PATCH net-next v7 2/2] virtio-net: Implement ndo_write_rx_mode callback

This refactor has the secondary benefit of stopping set rx_mode
requests from building up as only the most recent request (before the
work has gotten a chance to run) will be confirmed/executed. Does this
sound good enough to justify the refactor for drivers which do the I/O
under a driver specific spin lock?

On Tue, 6 Jan 2026 at 16:53, Xuan Zhuo <xuanzhuo@...ux.alibaba.com> wrote:

> If this is a common requirement, it would be better to provide more examples of
> driver modifications.
>
> Thanks.

I am planning on modifying these drivers which I can test with
QEMU/vng. Does this list sound good?

e1000
8139cp

(I will do these if the secondary benefit sounds useful)

vmxnet3
pcnet32