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: <20231016153548.1c050ea3@kernel.org> Date: Mon, 16 Oct 2023 15:35:48 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Jamal Hadi Salim <jhs@...atatu.com> Cc: netdev@...r.kernel.org, anjali.singhai@...el.com, namrata.limaye@...el.com, deb.chatterjee@...el.com, john.andy.fingerhut@...el.com, dan.daly@...el.com, Vipin.Jain@....com, tom@...anda.io, mleitner@...hat.com, Mahesh.Shirshyad@....com, tomasz.osinski@...el.com, jiri@...nulli.us, xiyou.wangcong@...il.com, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, vladbu@...dia.com, horms@...nel.org, khalidm@...dia.com, toke@...hat.com, mattyk@...dia.com Subject: Re: [PATCH v7 net-next 00/18] Introducing P4TC On Mon, 16 Oct 2023 17:44:20 -0400 Jamal Hadi Salim wrote: > > Verified from downloading mbox.gz from lore that the tarball was > > reordered. Dont know if it contributed - but now compiling patch by > > patch on the latest net-next tip. > > Never mind - someone pointed me to patch work and i can see some > warnings there. Looks like we need more build types and compiler > options to catch some of these issues. > We'll look into it and we will replicate in our cicd. patch-by-patch W=1 C=1 should be good enough to catch the problems.
Powered by blists - more mailing lists