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
| ||
|
Message-ID: <14584a37-2882-4cd8-9380-40a532d07731@linux.vnet.ibm.com> Date: Thu, 2 Nov 2023 15:37:04 -0500 From: Thinh Tran <thinhtr@...ux.vnet.ibm.com> To: Michael Chan <michael.chan@...adcom.com> Cc: netdev@...r.kernel.org, siva.kallam@...adcom.com, prashant@...adcom.com, mchan@...adcom.com, pavan.chebbi@...adcom.com, drc@...ux.vnet.ibm.com, venkata.sai.duggi@....com Subject: Re: [PATCH v2] net/tg3: fix race condition in tg3_reset_task() Thanks for the review. On 11/2/2023 12:27 PM, Michael Chan wrote: > > This scenario can affect other drivers too, right? Shouldn't this be > handled in a higher layer before calling ->ndo_tx_timeout() so we > don't have to add this logic to all the other drivers? Thanks. Yes, it does. We can add this into the dev_watchdog() function, but further investigations are required. This is because each driver may have a different approach to handling its own ->ndo_tx_timeout() function. Thinh Tran
Powered by blists - more mailing lists