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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 16 Dec 2020 04:35:04 +0300 From: Sergej Bauer <sbauer@...ckbox.su> To: Jakub Kicinski <kuba@...nel.org> Cc: patchwork-bot+netdevbpf@...nel.org, andrew@...n.ch, Markus.Elfring@....de, thesven73@...il.com, bryan.whitehead@...rochip.com, UNGLinuxDriver@...rochip.com, davem@...emloft.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v4] lan743x: fix for potential NULL pointer dereference with bare card On Wednesday, December 16, 2020 4:12:42 AM MSK Jakub Kicinski wrote: > On Tue, 15 Dec 2020 23:39:14 +0000 patchwork-bot+netdevbpf@...nel.org > > wrote: > > Hello: > > > > This patch was applied to bpf/bpf.git (refs/heads/master): > > > > On Tue, 15 Dec 2020 19:12:45 +0300 you wrote: > > > This is the 4th revision of the patch fix for potential null pointer > > > dereference with lan743x card. > > > > > > The simpliest way to reproduce: boot with bare lan743x and issue > > > "ethtool ethN" command where ethN is the interface with lan743x card. > > > Example: > > > > > > $ sudo ethtool eth7 > > > dmesg: ... > > > [...] > > > > Here is the summary with links: > > - [v4] lan743x: fix for potential NULL pointer dereference with bare > > card > > > > https://git.kernel.org/bpf/bpf/c/e9e13b6adc33 > > > > You are awesome, thank you! > > -- > > Deet-doot-dot, I am a bot. > > https://korg.docs.kernel.org/patchwork/pwbot.html > > Heh the bot got confused, I think. > > What I meant when I said "let's wait for the merge window" was that > the patch will not hit upstream until the merge window. It's now in > Linus's tree. I'll make a submission of stable patches to Greg at the > end of the week and I'll include this patch. > > Thanks! I think, firstly the bot was confused by me :-\ I should have asked you what exactly did you mean with "let's wait for the merge window"... That's completely my fault, sorry for that. Regards, Sergej.
Powered by blists - more mailing lists