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: Thu, 11 Aug 2022 10:23:10 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Jakub Sitnicki <jakub@...udflare.com> Cc: netdev@...r.kernel.org, kernel-team@...udflare.com, van fantasy <g1042620637@...il.com> Subject: Re: [PATCH net] l2tp: Serialize access to sk_user_data with sock lock On Wed, 10 Aug 2022 12:28:48 +0200 Jakub Sitnicki wrote: > Fixes: fd558d186df2 ("l2tp: Split pppol2tp patch into separate l2tp and ppp parts") That tag immediately sets off red flags. Please find the commit where to code originates, not where it was last moved. > Reported-by: van fantasy <g1042620637@...il.com> > Tested-by: van fantasy <g1042620637@...il.com> Can we get real names? Otherwise let's just drop those tags. I know that the legal name requirement is only for S-o-b tags, technically, but it feels silly.
Powered by blists - more mailing lists