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
| ||
|
Date: Tue, 3 May 2022 16:26:58 +0200 From: Ferry Toth <fntoth@...il.com> To: Lukas Wunner <lukas@...ner.de> Cc: Steve Glendinning <steve.glendinning@...well.net>, UNGLinuxDriver@...rochip.com, Oliver Neukum <oneukum@...e.com>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org, linux-usb@...r.kernel.org, Andre Edich <andre.edich@...rochip.com>, Oleksij Rempel <o.rempel@...gutronix.de>, Martyn Welch <martyn.welch@...labora.com>, Gabriel Hojda <ghojda@...urs.ro>, Christoph Fritz <chf.fritz@...glemail.com>, Lino Sanfilippo <LinoSanfilippo@....de>, Philipp Rosenberger <p.rosenberger@...bus.com>, Heiner Kallweit <hkallweit1@...il.com>, Andrew Lunn <andrew@...n.ch>, Russell King <linux@...linux.org.uk> Subject: Re: [PATCH net-next 0/7] Polling be gone on LAN95xx Hi On 03-05-2022 10:26, Lukas Wunner wrote: > On Mon, May 02, 2022 at 10:33:06PM +0200, Ferry Toth wrote: >> Op 27-04-2022 om 07:48 schreef Lukas Wunner: >>> Do away with link status polling on LAN95XX USB Ethernet >>> and rely on interrupts instead, thereby reducing bus traffic, >>> CPU overhead and improving interface bringup latency. >> Tested-by: Ferry Toth <fntoth@...il.com> (Intel Edison-Arduino) > Thank you! > >> While testing I noted another problem. I have "DMA-API: debugging enabled by >> kernel config" and this (I guess) shows me before and after the patches: >> >> ------------[ cut here ]------------ >> DMA-API: xhci-hcd xhci-hcd.1.auto: cacheline tracking EEXIST, overlapping >> mappings aren't supported > That is under investigation here: > https://bugzilla.kernel.org/show_bug.cgi?id=215740 > > It's apparently a long-standing bug in the USB core which was exposed > by a new WARN() check introduced in 5.14. I'm not sure this is correct. The issue happens for me only when connecting the SMSC9414. Other usb devices I have (memory sticks, wifi, bluetooth) do not trigger this. I think we need to consider it might be a valid warning. It seems to be originating from the same "Workqueue: usb_hub_wq hub_event" though. > Thanks, > > Lukas
Powered by blists - more mailing lists