[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250924195055.15735499.michal.pecio@gmail.com>
Date: Wed, 24 Sep 2025 19:50:55 +0200
From: Michal Pecio <michal.pecio@...il.com>
To: Petko Manolov <petkan@...leusys.com>
Cc: I Viswanath <viswanathiyyappan@...il.com>, kuba@...nel.org,
edumazet@...gle.com, andrew+netdev@...n.ch, davem@...emloft.net,
pabeni@...hat.com, linux-usb@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, skhan@...uxfoundation.org,
linux-kernel-mentees@...ts.linux.dev, david.hunter.linux@...il.com,
syzbot+78cae3f37c62ad092caa@...kaller.appspotmail.com
Subject: Re: [PATCH net v3] net: usb: Remove disruptive netif_wake_queue in
rtl8150_set_multicast
On Wed, 24 Sep 2025 16:58:14 +0300, Petko Manolov wrote:
> netif_[stop|wake]_queue() should have been removed from rtl8150_set_multicast()
> long time ago, but somehow it has slipped under the radar. As far as i can tell
> this is the only change needed.
Hi,
Glad to see that you are still around.
Do you happen to remember what was the reason for padding all TX frames
to at least 60 bytes?
This was apparently added in version "v0.5.0 (2002/03/28)".
I'm yet to test the exact effect of this hack (will the HW really send
frames with trailing garbage?) and what happens if it's removed (maybe
nothing bad? or was there a HW bug?), but this part caught my attention
because I think nowadays some people could consider it "information
leak" ;) And it looks like a waste of bandwidth at least.
Regards,
Michal
Powered by blists - more mailing lists